Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 636760

Summary: app-emulation/virtualbox-5.1.26, assertion failed
Product: Gentoo Linux Reporter: aeriksson2
Component: Current packagesAssignee: Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c>
Status: RESOLVED OBSOLETE    
Severity: normal CC: bkohler, masterzorag, proxy-maint
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description aeriksson2 2017-11-07 05:46:22 UTC
Moving for a stable 4.lastest to 5.1.26, I'm now greeted with this crash a few times a day (This one from 5.1.30, but I get this for 5.1.26 too). 

nsNativeComponentLoader: autoregistering begins.
nsNativeComponentLoader: autoregistering succeeded
nNCL: registering deferred (0)
WARNING: failed to send RELEASE event, file /var/tmp/portage/app-emulation/virtualbox-5.1.30/work/VirtualBox-5.1.30/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp, line 2338

<repeats for 91 lines>

WARNING: failed to send RELEASE event, file /var/tmp/portage/app-emulation/virtualbox-5.1.30/work/VirtualBox-5.1.30/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp, line 2338
Qt WARNING: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14207, resource id: 12676779, major code: 40 (TranslateCoords), minor code: 0

!!Assertion Failed!!
Expression: vbox.isOk() && !machine.isNull()
Location  : /var/tmp/portage/app-emulation/virtualbox-5.1.30/work/VirtualBox-5.1.30/src/VBox/Frontends/VirtualBox/src/extradata/UIExtraDataManager.cpp(2134) void UIExtraDataManager::setExtraDataString(const QString&, const QString&, const QString&)
Trace/breakpoint trap

Apart from this, I've received about half a dozen other backtraces and whatnot all leading up to a crash. Anyone know where I can fond the old 4.x ebuilds which have been tree cleaned? This is a production machine, and 5.1.26 is just not stable.
Comment 1 Ben Kohler gentoo-dev 2018-10-31 15:57:18 UTC
Please reopen if this still affects 5.2.x