crash after typing two letter in the 'alt'- osd

[Ondergetekende]

I typed two characters into the menu which pops up after pressing 'alt'. (not sure what that menu is called). No window was focussed.
It was supped to show the vpn connection, which starts with those two letters.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
CheckboxSubmission: f28d14011f93323ef50e1be333cb8ce1
CheckboxSystem: 669b662da410063cc918e0f60cf6cddf
Date: Thu Apr 12 17:27:13 2012
ExecutablePath: /usr/bin/unity-2d-shell
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: unity-2d-shell
SegvAnalysis:
 Segfault happened at: 0x7f801975fc2a <_ZNK10QDBusError7messageEv+10>: lock incl (%rdx)
 PC (0x7f801975fc2a) ok
 source "(%rdx)" (0x00000000) not located in a known VMA region (needed readable region)!
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 QDBusError::message() 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::message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse 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 #968046, 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.