While using HUD: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-2d (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I invoked the hud pressing the alt key but wanted to open the dash. I tried to press escape to close the hud with no success. Instead in the lower right corner of the screen a small text input field appeard and i could type text there instead of into the hud.
The the HUD crashed. Interestingly, the global menu appears a rather strange position in the top bar: somewhat near the center instead of the left corner (see the attached screenshot). Im not sure if this is related and if to fill a seperate bug.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.6.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
Date: Fri Mar 9 18:38:28 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: unity-2d-shell
SegvAnalysis:
Segfault happened at: 0x7f2c195b44d3 <_ZN22QDBusAbst
PC (0x7f2c195b44d3) ok
source "0x8(%rsi)" (0x00700077) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading unknown 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #947538, 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.