Unity 2d crashed unexpectedly. unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-2d (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Unity 2d was reported to have crashed after I pressed either the the alt-key or the command key - both were pressed a few times. VMware Fusion. Ubuntu 64-bit.
Expected event: Opening of the run command -dialog or opening of the search-dialog.
Occured event: Unity 2d was reported to have crashed.
Since then: normal behaviour.
Description: Ubuntu precise (development branch)
Release: 12.04
-------
unity-2d:
Installed: 5.10.0-0ubuntu1
-------
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.10.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
Date: Mon Apr 16 14:18:56 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: unity-2d-shell
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f28368d44dd <_ZN22QDBusAbst
PC (0x7f28368d44dd) ok
source "$0x0" ok
destination "0xd4(%rbp)" (0x000000d6) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
QDBusAbstractI
BamfView::icon() const () from /usr/lib/
WindowInfo::icon() const () from /usr/lib/
WindowInfo:
?? () from /usr/lib/
Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractIn
UpgradeStatus: Upgraded to precise on 2012-04-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #962647, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.