https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
Jason W. Bacon changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
w.schwarzenf...@utanet.at changed:
What|Removed |Added
CC||w.schwarzenf...@utanet.a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #22 from robert.ayrapet...@gmail.com ---
Ok, so here is what helped me after another 5 minutes of research...
pkg info | grep llvm
llvm39-3.9.1_4 LLVM and Clang
(so only one llvm is installed)
VirtualBox segfaul
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #23 from Jason Bacon ---
That fact that it worked as root does not mean it's a permissions issue. There
are many other variables between the root env and other envs. In my case, it
was PATH differences that caused it to work u
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
robert.ayrapet...@gmail.com changed:
What|Removed |Added
CC||robert.ayrapet...@gmai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #20 from Jason Bacon ---
FYI, llvm37 by itself is not sufficient to cause of this issue. In trying to
reproduce the problem, I found that even with llvm37 installed on my ThinkPad
with Intel graphics, I do not experience a cra
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #19 from Trenton Schulz ---
(In reply to rkoberman from comment #17)
Well, this explains lots of problems I was having in TrueOS with OpenGL (well,
Mesa). I'm glad I stumbled onto that bit of info. I removed all my llvm
orphans
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #18 from Jason Bacon ---
Looks like onlyu lang/rubinius *might* install it as a dep, and it's not a
default option. The other possibility is if someone installed clang37.
Nevertheless, it's a nasty issue for people to run int
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
rkober...@gmail.com changed:
What|Removed |Added
CC||rkober...@gmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #16 from Trenton Schulz ---
Yes, it seems the llvm37 causes havoc for me too. Removing it and everything
works again. Hooray. Though it seems there must be some sort of version
mismatch going on with different llvm versions. Fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #15 from Jason Bacon ---
The "Failed to acquire the VirtualBox COM object." error was caused by a
corrupt ~/.config/VirtualBox folder. Apparently it was created by either the
failed runs as a normal user, or the successful run
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #14 from Jason Bacon ---
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
Virtua
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #13 from Jason Bacon ---
I suspect you're right that it was triggered by a change outside virtualbox.
It's only the permissions issue that I have doubts about.
This is difficult to debug since gdb cannot honor setuid() for se
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #12 from Trenton Schulz ---
(In reply to Jason Bacon from comment #11)
Hmmm… OK. This is actually with a TrueOS (a.k.a. FreeBSD 12) build. The thing
is that just happened recently with an upgrade on TrueOS, but running an
earli
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #11 from Jason Bacon ---
I'd be surprised if it turned out to be permissions.
As a reminder, it works fine for me on some systems, but not others. My
Thinkpad T61 with Intel GPU runs VirtulBox fine, as does a dev server runni
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
Trenton Schulz changed:
What|Removed |Added
CC||free...@norwegianrockcat.co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #9 from Jason Bacon ---
For what it's worth, rolling back to 5.1.12 doesn't help. Perhaps the problem
was triggered by a dependency rather than the virtualbox upgrade. I'll try
earlier versions if the rollback is easy enough f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #8 from Graham Perrin ---
Created attachment 180308
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180308&action=edit
screenshot of the dialogue that appears following a truss run of VirtualBox
Transcript of the erro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #6 from Graham Perrin ---
Created attachment 180296
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180296&action=edit
terminal outputs from two boot environments
Boot environment
2017-02-25-05-22-57---custom-2dc2a76
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #7 from Graham Perrin ---
Created attachment 180297
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180297&action=edit
output from truss
Boot environment
2017-02-25-05-22-57---custom-2dc2a76-38-a
modesetting_drv.so
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #5 from Graham Perrin ---
TrueOS Desktop based on FreeBSD-CURRENT: VirtualBox does run, with KMS
(modesetting_drv.so) for graphics, with a boot environment that was created on
2017-02-11.
With more recent distributions of the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #4 from Jason Bacon ---
You may already have realized this, but it's not limited to AMD CPUs:
I just encountered the issue on an old Core 2 Duo iMac:
FreeBSD 10.3-RELEASE-p11 #0: Mon Oct 24 18:49:24 UTC 2016
r...@amd64-bui
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #3 from Graham Perrin ---
The tail of
http://www.virtualbox.org/svn/vbox/trunk/src/VBox/Frontends/VirtualBox/src/hardenedmain.cpp
(includes line 72):
#ifdef VIRTUALBOX_VM
return SUPR3HardenedMain("VirtualBoxVM",
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Comment #2 from Jason Bacon ---
Not getting a core when running as a normal user, and can't load the executable
into gdb due to lack of read permission. After a little experimenting...
<<>> /home/bacon 1008 # xauth add
sculpin.acadix
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
Steven Hartland changed:
What|Removed |Added
CC||s...@freebsd.org
--- Comment #1
Jason Bacon has reassigned Bugzilla Automation
's request for maintainer-feedback to v...@freebsd.org:
Bug 217258: emulators/virtualbox-ose: Segmentation fault on startup
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
--- Description ---
VirtualBox is seg faulting on startup on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217258
Bug ID: 217258
Summary: emulators/virtualbox-ose: Segmentation fault on
startup
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
27 matches
Mail list logo
