unity-2d-shell crashed with SIGSEGV in QDBusError::name()

[Natalia Bidart]

The "new" window that appears at the left top of the screen (the one that reads "type your command") was stuck and when it dissappeared, the apport crash report appeared.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
Date: Wed Apr 11 18:42:29 2012
ExecutablePath: /usr/bin/unity-2d-shell
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: unity-2d-shell
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f95ba16dc0a <_ZNK10QDBusError4nameEv+10>: lock incl (%rdx)
 PC (0x7f95ba16dc0a) ok
 source "(%rdx)" (0x7f95b8d2a9f0) ok
 SP (0x7fffabbbb758) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 QDBusError::name() const () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
 QDBusPendingCall::fromError(QDBusError const&) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
 QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList<QVariant> const&) () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
 BamfView::icon() const () from /usr/lib/libQtBamf.so.1
 WindowInfo::icon() const () from /usr/lib/libunity-2d-private.so.0
Title: unity-2d-shell crashed with SIGSEGV in QDBusError::name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #972817, 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.