|
Bugzilla – Full Text Bug Listing |
| Summary: | Virtualbox cannot be started on x86-64: Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Joop Boonen <joop.boonen> |
| Component: | Other | Assignee: | Martin Kudlvasr <mkudlvasr> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | kontakt, novell.admin, suse-tux |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Starting VirtualBox after the user was added to the vboxusers group | ||
|
Description
Joop Boonen
2008-09-18 08:26:45 UTC
}-Tux-{ fixed it already and will release a new package today. Until then you can run it as root.
*** Bug 426409 has been marked as a duplicate of this bug. *** You can find a fixed version in the Virtualization:VirtualBox repository. Sorry for the inconvenience. I'm sorry but as a normal user I still get an error on x86_64. I didn't check on ix86 32 yet.
The error is:
VirtualBox
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib64/virtualbox/VirtualBox.so",) failed: VBoxDDU.so: cannot open shared object file: No such file ordirectory
As root VirtualBox can be started without a problem.
Should be fixed with the new release (2.0.2-6.1) or does the problem still occur? I've just tested release virtualbox-ose-2.0.2-6.1 on both a 32 bits as 64 bits system works like a breeze. Thank you for your effort. As far as I'm concerned this "bug" has been resolved. * starts without root privileges * doesn't crash because of QGTKStyle * is able to start VM you fixed the bug. Still occurs in the 64 bit version of the final openSUSE11.1 (see the attached image). Created attachment 265325 [details]
Starting VirtualBox after the user was added to the vboxusers group
I mean Virtualbox cannot even be started on x86-64. I use vbox on my x86-64 machine with os11.1 and vbox from os11.1. I have never seen the error message you describe. Can you add more information, please? Vbox logs? OK, I started it from commandline: tamas@milleniumfalcon:~/.VirtualBox> VirtualBox Wrong owner (0) of '/tmp/.vbox-tamas-ipc'. Wrong owner (0) of '/tmp/.vbox-tamas-ipc'. It was the problem. Then I did this: tamas@milleniumfalcon:~/.VirtualBox> su Jelszó: milleniumfalcon:/home/tamas/.VirtualBox # ls -la /tmp/.vbox-tamas-ipc/ összesen 304 drwx------ 2 root root 4096 jan 15 13.56 . drwxrwxrwt 43 root root 299008 jan 28 19.48 .. srwx------ 1 root root 0 jan 15 13.56 ipcd -rw------- 1 root root 6 jan 15 13.56 lock milleniumfalcon:~ # chown tamas:users -R /tmp/.vbox-tamas-ipc And now VirtualBox runs without any problem. Even the sound works, much better than in openSUSE 11.0. Afterwards I exited the whole VirtualBox, removed the directory /tmp/.vbox-tamas-ipc, and restarted virtualbox, in order to observe, if it will be able to generate the new directory with appropriate permissions. And it was able! What generated that old and restrictive directory? I didn't do it manually. So, my problem is solved, but I don't know the orginal reason to help you avoiding this incident in the future. You said you were running vbox as root. So the tmp directory was created with root permissions. Regular user vbox was not able to delete them later. If you su to root, the tmp dir is still created with your name, but root (0) permissions. As the tmp dir is not deleted on vbox exit ... The PUEL version does the same thing. I'm lowering the severity since we already have a solution. I am going to work on the fix ... virtualbox was was taking the username from environment variables. I patched it to prefer username (as in getpwuid). Now root virtualbox creates his own tmp dir. Fixed in factory. |