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

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

Bug Description

This crash report appeared just after the first boot into a fresh install completed using the 20110830-i386 iso-testing image.

Just prior to this crash report I also got a crash report identical to bug 832603, though that may be unrelated.

The panel does however appear to be totally functional, and I got a slightly different crash report booting to the live desktop with the same image as described in posts 5 and 6 at bug 836755.

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: Tue Aug 30 04:30:37 2011
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110830)
ProcCmdline: unity-2d-panel
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xbe0937 <_ZNK11QConfSchema7findKeyEPKc+39>: mov 0x8(%eax),%edx
 PC (0x00be0937) 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

Revision history for this message
Erick Brunzell (lbsolost) wrote :
Revision history for this message
Erick Brunzell (lbsolost) wrote :

Oops, I see now that this is probably a dupe of bug 834045.

visibility: private → public
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.