gnome-settings-daemon crashed with SIGABRT in raise()

[gogo]

gnome-settings-daemon crashed with SIGABRT in raise()

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.3-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Jul 17 00:03:31 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110716)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCwd: /
ProcEnviron:
 LANG=hr_HR.UTF-8
 SHELL=/bin/false
 PATH=(custom, no user)
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: gnome-settings-daemon crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __assert_fail (assertion=0x7fee692b9c88 "req == dpy->xcb->pending_requests", file=<value optimized out>, line=140, function=<value optimized out>) at assert.c:81
 dequeue_pending_request (dpy=<value optimized out>, req=<value optimized out>) at ../../src/xcb_io.c:140
 _XReply (dpy=0x116ce50, rep=0x7fee609d9a80, extra=2, discard=0) at ../../src/xcb_io.c:574

[Pedro Villavicencio (pedro)]

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 804896, 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. Please continue to report any other bugs you may find.