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

[Jaime Rave]

I have just upgrade my 11.10 to 12.04 and when I started Gnome Shell the error appear.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic-pae 3.2.0-rc6
Uname: Linux 3.2.0-6-generic-pae i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CheckboxSubmission: d1d973974b16ca537194616ee72ade3e
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
Date: Fri Dec 23 01:00:38 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
SegvAnalysis:
 Segfault happened at: 0xb39b5e07: mov 0x4(%ebp),%edx
 PC (0xb39b5e07) ok
 source "0x4(%ebp)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/libsyncdaemon-1.0.so.1
 g_cclosure_marshal_VOID__POINTER (closure=0x907f8c8, return_value=0x0, n_param_values=2, param_values=0x907fd58, invocation_hint=0xbfc87420, marshal_data=0x0) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gmarshal.c:609
 ?? () from /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2
 g_closure_invoke (closure=0x907f8c8, return_value=0x0, n_param_values=3, param_values=0xb5904120, invocation_hint=0xbfc87420) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=0x8f98eb0, detail=1755, instance=0x8f82d28, emission_return=0x0, instance_and_params=0xb5904120) at /build/buildd/glib2.0-2.31.4.tested/./gobject/gsignal.c:3302
Title: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__POINTER()
UpgradeStatus: Upgraded to precise on 2011-12-23 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #907631, 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.