gsettings-data-convert crashed with SIGSEGV in gconf_client_get_default()

Bug #810797 reported by arpanaut
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
New
Undecided
Unassigned

Bug Description

Booted the daily-live desktop from July 14, 2011.
Opened the application lens, it immediately froze up and the crash notification showed up.
I looked at the other similar bug reports, they were all 64 bit and were on installed instances.
I'm on 32 bit and booted up on daily-live desktop iso.
Similar bug, different scenario I thought the information in this bug report would be helpful to Dev's.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gconf2 3.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic i686
Architecture: i386
CasperVersion: 1.271
Date: Thu Jul 14 22:51:03 2011
ExecutablePath: /usr/bin/gsettings-data-convert
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110714.1)
ProcCmdline: gsettings-data-convert
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3feb49: mov 0xc(%eax),%eax
 PC (0x003feb49) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gconf
StacktraceTop:
 ?? () from /usr/lib/libgconf-2.so.4
 gconf_client_get_default () from /usr/lib/libgconf-2.so.4
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: gsettings-data-convert crashed with SIGSEGV in gconf_client_get_default()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
arpanaut (johnmac) wrote :
visibility: private → public
Revision history for this message
Andrew Constantine (andrewmc) 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 810795, 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.

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.