VirtualBox crashed with SIGABRT in qt_message_output()

Bug #1208908 reported by James Michael DuPont on 2013-08-06
This bug affects 43 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)

Bug Description

After upgrading my distro, the dkms was not updated, the headers where not installed automatically and vbox was failing.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: virtualbox-qt 4.2.16-dfsg-1
ProcVersionSignature: Ubuntu 3.5.0-36.57-generic
Uname: Linux 3.5.0-36-generic i686
ApportVersion: 2.12-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Tue Aug 6 11:16:06 2013
ExecutablePath: /usr/lib/virtualbox/VirtualBox
InstallationDate: Installed on 2013-07-01 (36 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcCmdline: /usr/lib/virtualbox/VirtualBox --comment windoze --startvm 253b6f06-4b44-4bd1-8194-6be883e53d8c --no-startvm-errormsgbox
 PATH=(custom, no user)
Signal: 6
SourcePackage: virtualbox
 qt_message_output(QtMsgType, char const*) () from /usr/lib/i386-linux-gnu/
 ?? () from /usr/lib/i386-linux-gnu/
 qFatal(char const*, ...) () from /usr/lib/i386-linux-gnu/
 TrustedError () from /usr/lib/virtualbox/
 ?? ()
Title: VirtualBox crashed with SIGABRT in qt_message_output()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Changed in virtualbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu):
status: New → Confirmed
tags: added: trusty
information type: Private → Public
tags: added: utopic

I had this problem when upgrading 14.10 to 15.04beta
Manually installing virtualbox-dkms and "modprobe vboxdrv" solved the issue.

nazgul@rivendell:~$ LANG=C dpkg -la virtualbox*
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
ii virtualbox 4.3.22-dfsg-1 amd64 x86 virtualization solution - base binarie
un virtualbox-2.0 <none> <none> (no description available)
un virtualbox-2.1 <none> <none> (no description available)
un virtualbox-2.2 <none> <none> (no description available)
un virtualbox-3.0 <none> <none> (no description available)
un virtualbox-3.1 <none> <none> (no description available)
un virtualbox-3.2 <none> <none> (no description available)
un virtualbox-4.0 <none> <none> (no description available)
un virtualbox-4.1 <none> <none> (no description available)
un virtualbox-4.2 <none> <none> (no description available)
ii virtualbox-dkms 4.3.22-dfsg-1 all x86 virtualization solution - kernel modul
un virtualbox-guest-a <none> <none> (no description available)
ii virtualbox-guest-a 4.3.22-1 all guest additions iso image for VirtualBox
ii virtualbox-qt 4.3.22-dfsg-1 amd64 x86 virtualization solution - Qt based use
un virtualbox-source <none> <none> (no description available)

tags: added: vivid
Todd Cole (tcole3737) wrote :

dug a bit and found that Virtualbox could not locate a vm with UUID XXXXXXX-XXXX-XXX-XX__
 I then looked in /home/VirtualBox VMs found a extra file named Lubuntu Appliance in addition to the normal Lubuntu VM
as a test I moved it and all errors are now gone. I suspect it might be a fail start or shutdown VM report/log but it works so
I am happy

tags: added: xenial
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers