gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:515: _XReply: Assertion `!dpy->xcb->reply_data' failed.

[Jerry]

all sorts of problems, crashes since getting around the x windows login bug...

gnome-settings-daemon was racing (cpu 100%) last time I booted,
now all sorts of other crashes, I'd rather have it crash than burn out my CPU,
but still, so many bugs... Alpha... can't go back now...

Anyways, metacity crashed too, I do have some HPLIP type printer icon that
was on the panel last boot, but I closed it... Probably unrelated...

Good luck with this one, so many bugs I can't even WAG (Wild Arse Guess)
possible causes...

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic i686
Architecture: i386
AssertionMessage: gnome-settings-daemon: ../../src/xcb_io.c:515: _XReply: Assertion `!dpy->xcb->reply_data' failed.
CrashCounter: 1
Date: Thu Jul 14 18:00:33 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:
 LANG=en_US.UTF-8
 SHELL=/bin/false
 PATH=(custom, no user)
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:515: _XReply: Assertion `!dpy->xcb->reply_data' failed.
UpgradeStatus: Upgraded to oneiric on 2011-07-01 (13 days ago)
UserGroups:

[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 #804221, 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.