unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()

[S. Neumann]

I have some freezes, since I changed the unity version from 3d to 2d. This error is one of those.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Sun Apr 15 14:39:02 2012
ExecutablePath: /usr/bin/unity-2d-shell
InstallationMedia: Mythbuntu 9.10 "Karmic Koala" - Release i386 (20091028.4)
ProcCmdline: unity-2d-shell
SegvAnalysis:
 Segfault happened at: 0xb68c9fed <_ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+29>: mov 0x4(%esi),%edi
 PC (0xb68c9fed) ok
 source "0x4(%esi)" (0x00000003) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList<QVariant> const&) () from /usr/lib/i386-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
 WindowInfo::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libunity-2d-private.so.0
 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
Title: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()
UpgradeStatus: Upgraded to precise on 2012-03-24 (21 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin mythtv netdev plugdev sambashare tape vboxusers video

[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 #979936, 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.