VirtualBox crashed with SIGSEGV in MenuBarAdapter::registerWindow()

Bug #1545852 reported by Jake McGregor on 2016-02-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)

Bug Description

afI was attempting to add several existing VM's to VirtualBox when it crashed. After VirtualBox restarted, I was able to import them fine, as well as start them.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: virtualbox-qt 5.0.14-dfsg-2
ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1
Uname: Linux 4.4.0-5-generic x86_64
ApportVersion: 2.20-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 15 14:38:07 2016
ExecutablePath: /usr/lib/virtualbox/VirtualBox
InstallationDate: Installed on 2016-02-02 (13 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/virtualbox/VirtualBox --comment Windows\ 10 --startvm bacfe9bd-85bf-486e-9289-29aa19dcd261 --no-startvm-errormsgbox
 Segfault happened at: 0x7f5e20a490e0 <_ZN14MenuBarAdapter14registerWindowEv+1344>: decl -0x77(%rax)
 PC (0x7f5e20a490e0) ok
 source "-0x77(%rax)" (0x7f5e20a49069) ok
 SP (0x7ffcbb8768f8) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: virtualbox
 MenuBarAdapter::registerWindow() () from /usr/lib/x86_64-linux-gnu/qt4/plugins/menubar/
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: VirtualBox crashed with SIGSEGV in MenuBarAdapter::registerWindow()
UpgradeStatus: Upgraded to xenial on 2016-02-02 (13 days ago)
UserGroups: adm libvirtd lpadmin sambashare sudo

Jake McGregor (jake-mcgregor86) wrote :

 ~Stream (this=0x26e2ce0, __in_chrg=<optimized out>) at /usr/include/qt4/QtCore/qdebug.h:64
 ~QDebug (this=0x7ffcbb876948, __in_chrg=<optimized out>) at /usr/include/qt4/QtCore/qdebug.h:88
 MenuBarAdapter::registerWindow (this=<optimized out>) at /build/buildd/appmenu-qt-0.2.7+14.04.20140305/src/appmenuplatformmenubar.cpp:404
 ?? ()
 ?? ()

tags: removed: need-amd64-retrace
Jake McGregor (jake-mcgregor86) wrote :

It appears this bug has happened again, except I wasn't using VirtualBox as well. The system was sitting idle.

Jake McGregor (jake-mcgregor86) wrote :

Well, I see I'm reporting my own bug again. The only notable difference from then is that I am now running 16.04 beta. I was attempting to start a Windows 10 virtual machine, but it failed to start. When trying again it worked fine.

information type: Private → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers