VirtualBox segfaults on 10.0-CURRENT

[Miguel C.]

I have a similar report in the list... I'm able to run VirtualBox with sudo -u myuser had a workarround.  But I'm not sure why it works. 


Piotr Kubaj <pkubaj at riseup.net> wrote:
>I've upgraded recently from 9.2-RELEASE to 10.0-CURRENT. At first,
>VirtualBox reported the lack of /usr/lib/libstdc++.so.6, even though it
>was compiled with lang/gcc (it was after WITHOUT_GCC and WITHOUT_GNUCXX
>became default for amd64). Then, I've tried to buildworld with WITH_GCC
>and WITH_GNUCXX and build VirtualBox with base gcc, but it reports an
>error. After that and starting with a fresh test user, VirtualBox
>started to segfault, without any *.core files. When I try to run
>VBoxManage createvm, it reports:
>~/ VBoxManage createvm
>VBoxManage: error: Failed to create the VirtualBox object!
>VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted
>(extended info not available)
>VBoxManage: error: Most likely, the VirtualBox COM server is not
>running
>or failed to start.
>
>Rebuilding with default options doesn't help.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.