unity-2d-panel crashed with SIGSEGV in QConf::notify()

[Rachid Achellal]

crashed after login

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-panel 4.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-server 3.0.3
Uname: Linux 3.0.0-9-server x86_64
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 29 23:31:31 2011
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2)
ProcCmdline: unity-2d-panel
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f565dbb1152 <_ZN5QConf6notifyEPKc+18>: mov 0x8(%rax),%rdx
 PC (0x7f565dbb1152) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 QConf::notify(char const*) () from /usr/lib/libdconf-qt.so.0
 ?? () from /usr/lib/libdconf-dbus-1.so.0
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
Title: unity-2d-panel crashed with SIGSEGV in QConf::notify()
UpgradeStatus: Upgraded to oneiric on 2011-08-26 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 QConf::notify(char const*) () from /tmp/tmp5zvtWG/usr/lib/libdconf-qt.so.0
 add_match_done (pending=<optimized out>, user_data=0x12616c0) at dconf-dbus-1.c:569
 ?? () from /tmp/tmp5zvtWG/lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /tmp/tmp5zvtWG/lib/x86_64-linux-gnu/libdbus-1.so.3
 q_dbus_connection_dispatch (connection=<optimized out>) at qdbus_symbols_p.h:115

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #834001, so it 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. Feel free to continue to report any other bugs you may find.