Date: Wed, 01 Mar 2017 20:43:21 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: [Bug 217258] emulators/virtualbox-ose: Segmentation fault on startup Message-ID: <bug-217258-26505-TLcBLFEQKK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217258-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-217258-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217258 --- Comment #14 from Jason Bacon <bacon4000@gmail.com> --- On my 10.3 systems, doing the following resolved the issue: pkg delete llvm37 pkg delete virtualbox\* (for good measure) pkg autoremove (for good measure) pkg upgrade pkg install virtualbox-ose VirtualBox now opens normally. I'm not sure where the llvm37 installation came from. My guess is is was orphaned by pkg upgrade when it upgraded to llvm39. I'm getting a different error on my 11.0 system, but I don't think it's related. Popup error box: Failed to acquire the VirtualBox COM object. Callee RC:=20 NS_BASE_STREAM_WOULD_BLOCK (0x80470007) So it appears the VirtualBox should protect against loading llvm37 librarie= s if they're present. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217258-26505-TLcBLFEQKK>