Opened 4 years ago
Closed 4 years ago
#19059 closed defect (invalid)
VboxLinuxAdditions.run file corrupt
Reported by: | abrasax | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 6.0.14 |
Keywords: | installation | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
The crux of the issue:
The VBoxLinuxAdditions.run file is missing an EOF character which is causing the next file on the media, VBoxGuestAdditions-x86.tar.bz2, to be included in the file contents. Fortunately, Linux is smart enough to realize that this is wrong and doesn't execute the file. Instead, it opens the file(s) in a text editor where you are instructed to fix it. At first, I thought I might be able to fix it. But upon further investigation, it turns out that I do not know how to fix it.
Steps to reproduce (although they shouldn't really be necessary):
- I installed VirtualBox 6.0.14 from the publicly released media.
- I created a new VM and installed Debian 10.1
- I logged into the new VM and immediately mounted the VirtualBox Guest Additions using the Devices menu option.
- When Debian asked what I wanted to do with the new media, I opted to open in the file manager.
- I then double-clicked on VBoxLinuxAdditions.run to begin installation as I have done countless times in the past (with older versions).
- Instead of running, the file was opened in a text editor and helpful dialog explained that invalid characters were detected in the file and that I needed to fix this before it could be executed.
- I scrolled down a ways and saw where the UTF-8 text file (shell script, obv) changed into a binary file. See attached screenshot.
Attachments (1)
Change History (3)
by , 4 years ago
Attachment: | vb-bug.png added |
---|
comment:1 by , 4 years ago
Just for the sake of clarity, I'd like to add an elaboration to the steps to reproduce:
1a. I installed the Guest Additions using the dialog that pops up when you run VB for the first time after a new install. The dialog downloaded and installed Guest Additions and then I opted to delete the installer file. No errors were reported.
comment:2 by , 4 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
The file is not corrupt. This is a self-extracting archive and is exactly as intended.
Screenshot of file corruption