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

Bug #837346 reported by El Pensador
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-2d (Ubuntu)
New
Undecided
Unassigned

Bug Description

After logging in, the desktop and the dock appear and I get this error. However, unity 2D seems to work fine.

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
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Tue Aug 30 14:13:42 2011
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110817)
ProcCmdline: unity-2d-panel
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x115937 <_ZNK11QConfSchema7findKeyEPKc+39>: mov 0x8(%eax),%edx
 PC (0x00115937) 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: Upgraded to oneiric on 2011-08-25 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
El Pensador (el-pensador) wrote :
visibility: private → public
Revision history for this message
Robert Roth (evfool) wrote :

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.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.