GNOME Bugzilla – Bug 657255
gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:575: _XReply: Assertion `!xcb_xlib_extra_reply_data_left' failed.
Last modified: 2011-09-18 14:07:56 UTC
this report has been filed here: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/832513 crashes when login ".
+ Trace 228185
Thread 1 (Thread 0xb63feb70 (LWP 1187))
Backtrace stopped: Not enough registers or memory available to unwind further"
Could well be the same cause as bug 657241, X calls from multiple threads without proper protection.
This looks like a GSettings bug.
*** Bug 657630 has been marked as a duplicate of this bug. ***
*** Bug 655521 has been marked as a duplicate of this bug. ***
*** Bug 655829 has been marked as a duplicate of this bug. ***
*** Bug 657241 has been marked as a duplicate of this bug. ***
*** Bug 655910 has been marked as a duplicate of this bug. ***
on master: commit 27fbaf371278e792c79a3478c2282e43f12472f5 Author: Ryan Lortie <desrt@desrt.ca> Date: Tue Sep 6 14:01:52 2011 -0400 GSettingsBackend: emit changes to correct thread When g_settings_apply() is called on a delayed settings backend and there is a D-Bus error when communicating with dconf-service, recent versions of the dconf GSettingsBackend call a function in GLib that improperly delivered the signal directly instead of using g_main_context_invoke(). This patch fixes this function to route in the same way as the others so that the signal is dispatched in the proper GMainContext. Seb is going to ship this as a vendor patch to the just-released 2.29.90 to see if it fixes the problem. If it works, I'll backport to glib-2-30 and close this bug.
I guess no news is good news from the Ubuntu guys. I applied this patch to glib-2-30 branch as well.