unity-2d-panel crashed with SIGSEGV in QConfSchema::findKey()

[jerrylamos]

Oneiric updated as of today 25 August on T40 thinkpad. Note Unity defaults to something like Unity-2D but I installed Unity-2D with Synaptic a couple weeks ago.

Had just booted and was sitting there, then this error popped up.

Jerry

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-panel 4.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Date: Thu Aug 25 17:08:22 2011
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110724)
ProcCmdline: unity-2d-panel
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x925937 <_ZNK11QConfSchema7findKeyEPKc+39>: mov 0x8(%eax),%edx
 PC (0x00925937) ok
 source "0x8(%eax)" (0xffff95c0) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 QConfSchema::findKey(char const*) const () from /usr/lib/libdconf-qt.so.0
 QConf::notify(char const*) () from /usr/lib/libdconf-qt.so.0
 ?? () from /usr/lib/libdconf-qt.so.0
 ?? () from /usr/lib/libdconf-dbus-1.so.0
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
Title: unity-2d-panel crashed with SIGSEGV in QConfSchema::findKey()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 QConfSchema::findKey(char const*) const () from /tmp/tmplc9NyD/usr/lib/libdconf-qt.so.0
 QConf::notify(char const*) () from /tmp/tmplc9NyD/usr/lib/libdconf-qt.so.0
 ?? () from /tmp/tmplc9NyD/usr/lib/libdconf-qt.so.0
 add_match_done (pending=0x9fbbca0, user_data=0x9f2d580) at dconf-dbus-1.c:569
 ?? () from /tmp/tmplc9NyD/lib/i386-linux-gnu/libdbus-1.so.3

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