Opened 7 years ago
Last modified 5 years ago
#17104 awaitsfeedback defect
5.1.28 Guest Additions Install fails with gnome-terminal 3.24.2
| Reported by: | septer012 | Owned by: | |
|---|---|---|---|
| Component: | guest additions | Version: | VirtualBox 5.1.28 |
| Keywords: | gnome-terminal | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
The installation of guest additions fails with gnome-terminal version do to deprecated commands in install command.
localhost ~]$ /bin/gnome-terminal --version GNOME Terminal 3.24.2 Using VTE version 0.48.3 +GNUTLS
localhost ~]$ sudo sh /run/media/djohnson/VBOXADDITIONS_5.1.28_117968/autorun.sh
Here is the command that fails in the shell script:
+ BINARY='/run/media/djohnson/VBOXADDITIONS\_5\.1\.28\_117968/VBoxLinuxAdditions\.run' + exec /bin/gnome-terminal --title 'VirtualBox Guest Additions installation' -x /bin/sh /run/media/djohnson/VBOXADDITIONS_5.1.28_117968/runasroot.sh --has-terminal 'VirtualBox Guest Additions installation' '/bin/sh /run/media/djohnson/VBOXADDITIONS\_5\.1\.28\_117968/VBoxLinuxAdditions\.run --xwin' 'Please try running "/run/media/djohnson/VBOXADDITIONS_5.1.28_117968/VBoxLinuxAdditions.run" manually.' Option “-x” is deprecated and might be removed in a later version of gnome-terminal. Use “-- ” to terminate the options and put the command line to execute after it. Option “--title” is deprecated and might be removed in a later version of gnome-terminal. No protocol specified Unable to init server: Could not connect: Connection refused Failed to parse arguments: Cannot open display:
Change History (2)
comment:1 by , 5 years ago
comment:2 by , 5 years ago
| Status: | new → awaitsfeedback |
|---|
pls. use the latest supported 5.2 version, which is 5.2.34 for reporting problems:
https://www.virtualbox.org/wiki/Download_Old_Builds_5_2
can you confirm the problem does still exist with this?
Note:
See TracTickets
for help on using tickets.


Most likely, this is due to a lack of dependencies, when I ran into this on CentOS 8 box, I did this to resolve the problem:
The autorun script should check for these dependencies and report what is missing (and not such a cryptic error message).