Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 348010 - app-emulation/virtualbox-bin-3.2.12 fails to start on hardened - Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)
Summary: app-emulation/virtualbox-bin-3.2.12 fails to start on hardened - Callee RC: N...
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Patrick Lauer
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-07 08:05 UTC by mikopp
Modified: 2013-11-16 16:14 UTC (History)
3 users (show)

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

Attachments
emerge --info (emerge.info,4.66 KB, text/plain)
2010-12-14 17:51 UTC, mikopp 		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 mikopp 2010-12-07 08:05:38 UTC 
When started normally it fails with a pop saying 
"Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)"

This bug seems to do with a hardened build and location of binaries.
Fact is it does not work when starting /usr/bin/VirtualBox (the symlink) but does work fine when starting /opt/VirtualBox/VirtualBox

Also see http://www.virtualbox.org/ticket/3672#comment:28
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2010-12-09 18:52:48 UTC 
Please post your `emerge --info' in a comment.
Comment 2 mikopp 2010-12-14 17:51:59 UTC 
Created attachment 257158 [details]
emerge --info
Comment 3 Ben Kohler gentoo-dev 2013-10-02 22:55:24 UTC 
I can reproduce this same error if I immediately try to launch "VirtualBox" without relogging (or doing "source /etc/profile") for the new VBOX_APP_HOME="/opt/VirtualBox" variable from /etc/env.d/90virtualbox to take effect.  Does this error still happen if that variable is set in the environment from which you call VirtualBox?
Comment 4 Ben Kohler gentoo-dev 2013-11-16 16:14:06 UTC 
If you are still able to reproduce this after relogging (so proper env vars are set), please reopen.