Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 351109 - app-emulation/virtualbox-3.2.12-r3 does not start (it is looking for virtualbox-ose dir)
Summary: app-emulation/virtualbox-3.2.12-r3 does not start (it is looking for virtualb...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High major
Assignee: Lars Wendler (Polynomial-C) (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-08 12:01 UTC by Róbert Čerňanský
Modified: 2011-01-08 14:22 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Output of emerge --info (emerge-info,6.01 KB, text/plain)
2011-01-08 12:02 UTC, Róbert Čerňanský 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Róbert Čerňanský 2011-01-08 12:01:13 UTC 
It seems that recent renaming of virtualbox-ose to virtualbox broke it.

The file /etc/vbox/vbox.cfg contains value for INSTALL_DIR that points to "/usr/lib64/virtualbox-ose" which does not exists thus /usr/bin/VirtualBox wrapper script fails:

$ VirtualBox 
/usr/bin/VirtualBox: line 84: /usr/lib64/virtualbox-ose/VirtualBox: No such file or directory
/usr/bin/VirtualBox: line 84: exec: /usr/lib64/virtualbox-ose/VirtualBox: cannot execute: No such file or directory

Unfortunately fixing the value to "INSTALL_DIR=/usr/lib64/virtualbox" still does not make the VirtualBox to run.  Breakage seems to be somewhere in the library link level.  For example VBoxManage command does not find VBoxDDU.so which is located in /usr/lib64/virtualbox.

$ VBoxManage 
/usr/lib64/virtualbox/VBoxManage: error while loading shared libraries: VBoxDDU.so: cannot open shared object file: No such file or directory

or

$ VirtualBox 
VirtualBox: supR3HardenedVerifyDir: Failed to open "/usr/lib64/virtualbox-ose": No such file or directory (2)


Vbox modules are loaded:

$ lsmod | grep vbox
vboxnetflt             12973  0 
vboxnetadp              4172  0 
vboxdrv              1732527  2 vboxnetflt,vboxnetadp


Environment is set:

$ echo $VBOX_APP_HOME 
/usr/lib64/virtualbox


Relevant USE flags settings:

# emerge -pv virtualbox
...
[ebuild   R   ] app-emulation/virtualbox-3.2.12-r3  USE="additions alsa opengl python qt4 vnc -headless -pulseaudio -sdk -vboxwebsrv" 0 kB


This was the first install of VirtualBox on this machine.
Comment 1 Róbert Čerňanský 2011-01-08 12:02:52 UTC 
Created attachment 259284 [details]
Output of emerge --info
Comment 2 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2011-01-08 12:32:32 UTC 
please make sure that you

1) etc-update all virtualbox related files after the upgrade
2) run "env-update" as root after the upgrade
3) logout and relogin with the user you want to run virtualbox as

Please report back if these three steps help to fix your issue.
Comment 3 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2011-01-08 12:41:06 UTC 
+  08 Jan 2011; Lars Wendler <polynomial-c@gentoo.org>
+  -virtualbox-3.2.12-r3.ebuild, virtualbox-3.2.12-r4.ebuild,
+  files/virtualbox-ose-3-config:
+  Fixed install path in vbox.cfg. Thanks to Robert Cernansky for reporting this
+  issue in bug #351109.

Forget my previous comment. I forgot to adjust the install path in two files (stupid me!). Sorry for the inconveniencies. Should be fixed with virtualbox-3.2.12-r4.
Comment 4 Róbert Čerňanský 2011-01-08 14:22:23 UTC 
It works now.  Many thanks for such a quick response!