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

[dino99]

Oneiric i386

got this crash following these steps:
- fresh boot
- open nautilus to watch .xsession-errors
and the crash hapened

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gconf2 3.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic-pae 3.0.0-rc7
Uname: Linux 3.0.0-5-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu Jul 14 12:19:01 2011
ExecutablePath: /usr/bin/gsettings-data-convert
ProcCmdline: gsettings-data-convert
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb7781b49: mov 0xc(%eax),%eax
 PC (0xb7781b49) 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 audio avahi avahi-autoipd boinc cdrom couchdb crontab daemon debian-tor dialout disk fuse haldaemon klog kmem libuuid lpadmin mail messagebus mlocate mysql mythtv netdev ntp operator plugdev polkituser pulse root sambashare saned shadow ssh ssl-cert sudo syslog tty users utmp video voice www-data

[Susan Cragin (susancragin)]

I had probably same crash, have similar setup but have Lenovo X201 tablet, 64-bit oneiric, do not have nvidia

[jerrylamos (jerrylamos)]

14 July daily build live booted and got this error on Aspire 5253 notebook.

Jerry

[shoo_ash (ash-mail)]

Keep getting this bug every time I reboot.

[Apport retracing service (apport)]

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