gnome-settings-daemon crashed with SIGSEGV in translate_bool_int()

[Michael Moroni]

Crash when loading Ubuntu

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.91-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
Architecture: i386
Date: Tue Sep 6 11:45:13 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x2f5a1d3: mov (%eax),%ecx
 PC (0x02f5a1d3) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
 g_flags_register_static () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
Title: gnome-settings-daemon crashed with SIGSEGV in g_flags_register_static()
UpgradeStatus: Upgraded to oneiric on 2011-09-06 (1 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 translate_bool_int (manager=0x8bebfb8, trans=0x2f61410, value=0x8c1d1a8) at gsd-xsettings-manager.c:127
 process_value (value=0x8c1d1a8, trans=0x2f61410, manager=0x8bebfb8) at gsd-xsettings-manager.c:531
 xsettings_callback (manager=0x8bebfb8, key=0x8b72444 "event-sounds", settings=0x8bebf40) at gsd-xsettings-manager.c:576
 xsettings_callback (settings=0x8bebf40, key=0x8b72444 "event-sounds", manager=0x8bebfb8) at gsd-xsettings-manager.c:556
 g_flags_register_static (name=0x8bebfb8 "pw\277\b\001", const_static_values=0xa3e04e) at /build/buildd/glib2.0-2.29.90/./gobject/genums.c:230

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is that still an issue?
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.