unity-2d-panel crashed with SIGSEGV in unity::indicator::DBusIndicators::Impl::RequestSyncAll()

[Christian Theune]

Happened after running "disper -e -t left" twice. The first invocation didn't actually activate the second display.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-panel 5.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sun Jan 22 18:33:54 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: unity-2d-panel
SegvAnalysis:
 Segfault happened at: 0x7f5abb97cef5 <_ZN5unity9indicator14DBusIndicators4Impl14RequestSyncAllEv+117>: mov %rax,0x8(%rsi)
 PC (0x7f5abb97cef5) ok
 source "%rax" ok
 destination "0x8(%rsi)" (0x2f0027003d0070) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 unity::indicator::DBusIndicators::Impl::RequestSyncAll() () from /usr/lib/libunity-core-5.0.so.5
 unity::indicator::DBusIndicators::Impl::OnRemoteProxyReady(_GDBusProxy*) () from /usr/lib/libunity-core-5.0.so.5
 ?? () from /usr/lib/libunity-core-5.0.so.5
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: unity-2d-panel crashed with SIGSEGV in unity::indicator::DBusIndicators::Impl::RequestSyncAll()
UpgradeStatus: Upgraded to precise on 2012-01-21 (1 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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