Custom Query (16363 matches)
Results (493 - 495 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5475 | fixed | vboxadds fail on x64 systems -> fixed in 3.1 | ||
| Description |
[axet@axet-laptop ~]$ sudo /etc/init.d/vboxadd-x11 setup Setting up the X Window System drivers [FAILED] (Invalid Guest Additions configuration found) lib_dir="/usr/lib/VBoxGuestAdditions"
|
|||
| #5472 | fixed | vboxadditioins_3.0.10_54097/autorun.sh fails in Solaris 10 U8 (10/09) x86 Guest => Fixed in SVN | ||
| Description |
vboxadditioins_3.0.10_54097/autorun.sh fails in Solaris 10 U8 (10/09) x86 Guest
autorun.sh tries to run Workaround: put /usr/xpg4/bin at the front of the PATH. ( /usr/xpg4/bin/id does support '-u' ) See attachment for exact script output. |
|||
| #18853 | fixed | vboxadd.service unmounting vboxsf may return wrong error | ||
| Description |
On Linux, the service (script) /opt/VBoxGuestAdditions-5.2.32/init/vboxadd does shared folder(s) unmounting with: if ! umount -a -t vboxsf 2>/dev/null; then fail "Cannot unmount vboxsf folders" fi However umount may return an error if, for example, the same mount is available in more than one place, through binding. Then after first unmount of the same share the next one will be erroneous and umount may return error (on my Linux/Fedora it returns code 32). I'm suggesting to slightly modify that script to avoid (possibly wrong) error exit (which can annoy your logs ), as below: if ! umount -a -t vboxsf 2>/dev/null; then [ -n "$(findmnt -t vboxsf)" ] && fail "Cannot unmount vboxsf folders" fi |
|||

