the virtualbox port stopped working. If I try to start virtualbox it takes ages (10-15 minutes) until an error popup appears which shows the following message:
Failed to create the VirtualBox COM object.
The application will now terminate.
Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)
# uname -a
FreeBSD thor.rostock.home 10.1-RELEASE-p6 FreeBSD 10.1-RELEASE-p6 #0: Tue Feb 24 19:00:21 UTC 2015 firstname.lastname@example.org:/usr/obj/usr/src/sys/GENERIC amd64
# pkg info | grep virtualbox-ose
virtualbox-ose-4.3.26 General-purpose full virtualizer for x86 hardware
virtualbox-ose-kmod-4.3.26 VirtualBox kernel module for FreeBSD
I'm not really sure which update did this. Some days ago it was running without problems. But I can reproduce the problem on three machines all on 10.1, same patchlevel, same ports.
I am having the same problem also.
One short term (but unpleasant) workaround which worked for me is to run "VirtualBox" in a terminal, wait 5-10 seconds, kill VirtualBox with Control-C, wait another 5-10 seconds, and then run "VirtualBox" again in a terminal.
Are you running virtualbox from ports or from binary packages?
This is said to be related to the OpenSSL version upgrade to 1.0.2
Just downloaded the binary packages from pkg.freebsd.org, these link openssl libs even though the port does not define USE_OPENSSL= yes which is a mistake to begin with...
If you'd have curl built with ports OpenSSL you will have a conflict in the ssl libs.
Sorry for the late answer, I had a marriage to do. =)
I'm using virtualbox from ports. Today I've had some time to dig into this and I found out that /usr/local/lib/virtualbox/VBoxRT.so was using libcrypto from ports _and_ from base. This seems to indicate that the recent openssl upgrade may indeed be the problem.
I was able to solve this issue by recompiling curl with GSSAPI_NONE.
Did I understand this right? Is it solved? So it could be closed.
(In reply to w.schwarzenfeld from comment #5)
Seems so. =)
So please, close the PR, thanks!