unity-2d-panel crashed with SIGSEGV in IndicatorsWidget::onEntryRemoved()

[Jean-Baptiste Mazon]

I noticed while coming back from a DOSBox full-screen session, so it might either be that or have happened in the meantime.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-panel 4.6.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Sun Sep 11 22:40:25 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: unity-2d-panel
SegvAnalysis:
 Segfault happened at: 0x7f1953b9c823 <_ZN16IndicatorsWidget14onEntryRemovedERKSs+131>: mov (%rdx),%rsi
 PC (0x7f1953b9c823) ok
 source "(%rdx)" (0x29ba8f3d8) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 IndicatorsWidget::onEntryRemoved(std::string const&) () from /usr/lib/libunity-2d-private.so.0
 unity::indicator::Indicator::~Indicator() () from /usr/lib/libunity-core-4.0.so.4
 boost::detail::sp_counted_impl_p<unity::indicator::Indicator>::dispose() () from /usr/lib/libunity-core-4.0.so.4
 QList<boost::shared_ptr<unity::indicator::Indicator> >::~QList() () from /usr/lib/libunity-2d-private.so.0
 IndicatorsWidget::~IndicatorsWidget() () from /usr/lib/libunity-2d-private.so.0
Title: unity-2d-panel crashed with SIGSEGV in IndicatorsWidget::onEntryRemoved()
UpgradeStatus: Upgraded to oneiric on 2011-09-03 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (gwibber-service:4042): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #845773, 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.