After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 657255 - gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:575: _XReply: Assertion `!xcb_xlib_extra_reply_data_left' failed.
gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io...
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gsettings
unspecified
Other All
: High critical
: ---
Assigned To: Allison Karlitskaya (desrt)
gtkdev
: 655521 655829 655910 657241 657630 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-08-24 14:46 UTC by Pedro Villavicencio
Modified: 2011-09-18 14:07 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-08-24 14:46:17 UTC
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/832513

crashes when login 

".

Thread 1 (Thread 0xb63feb70 (LWP 1187))

  • #0 __kernel_vsyscall
  • #1 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #2 __GI_abort
    at abort.c line 92
  • #3 __GI___assert_fail
    at assert.c line 81
  • #4 _XReply
    at ../../src/xcb_io.c line 574
  • #5 XSync
    at ../../src/Sync.c line 44
  • #6 set_server_from_gsettings
    at gsd-a11y-keyboard-manager.c line 346
  • #7 keyboard_callback
    at gsd-a11y-keyboard-manager.c line 953
  • #8 g_cclosure_marshal_VOID__STRING
    at /build/buildd/glib2.0-2.29.16/./gobject/gmarshal.c line 504
  • #9 g_closure_invoke
    at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c line 773
  • #10 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3271
  • #11 g_signal_emit_valist
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3002
  • #12 g_signal_emit
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3059
  • #13 g_settings_real_change_event
    at /build/buildd/glib2.0-2.29.16/./gio/gsettings.c line 277
  • #14 ffi_call_SYSV
    at ../src/x86/sysv.S line 64
  • #15 ffi_call
    at ../src/x86/ffi.c line 303
  • #16 g_cclosure_marshal_generic
    at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c line 1146
  • #17 g_type_class_meta_marshal
    at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c line 884
  • #18 g_closure_invoke
    at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c line 773
  • #19 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3309
  • #20 g_signal_emit_valist
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3012
  • #21 g_signal_emit
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3059
  • #22 settings_backend_keys_changed
    at /build/buildd/glib2.0-2.29.16/./gio/gsettings.c line 387
  • #23 g_settings_backend_changed_tree
    at /build/buildd/glib2.0-2.29.16/./gio/gsettingsbackend.c line 700
  • #24 dconf_settings_backend_outstanding_returned
    at dconfsettingsbackend.c line 275
  • #25 g_simple_async_result_complete
    at /build/buildd/glib2.0-2.29.16/./gio/gsimpleasyncresult.c line 749
  • #26 g_dbus_connection_call_done
    at /build/buildd/glib2.0-2.29.16/./gio/gdbusconnection.c line 5034
  • #27 g_simple_async_result_complete
    at /build/buildd/glib2.0-2.29.16/./gio/gsimpleasyncresult.c line 749
  • #28 complete_in_idle_cb
    at /build/buildd/glib2.0-2.29.16/./gio/gsimpleasyncresult.c line 761
  • #29 g_idle_dispatch
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 4780
  • #30 g_main_dispatch
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 2439
  • #31 g_main_context_dispatch
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3008
  • #32 g_main_context_iterate
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3086
  • #33 g_main_loop_run
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3294
  • #34 dconf_context_thread
    at dconfcontext.c line 11
  • #35 g_thread_create_proxy
    at /build/buildd/glib2.0-2.29.16/./glib/gthread.c line 1962
  • #36 start_thread
    at pthread_create.c line 304
  • #37 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130
Backtrace stopped: Not enough registers or memory available to unwind further"
Comment 1 Matthias Clasen 2011-08-25 00:56:25 UTC
Could well be the same cause as bug 657241, X calls from multiple threads without proper protection.
Comment 2 Allison Karlitskaya (desrt) 2011-09-06 14:34:15 UTC
This looks like a GSettings bug.
Comment 3 Bastien Nocera 2011-09-06 14:39:10 UTC
*** Bug 657630 has been marked as a duplicate of this bug. ***
Comment 4 Bastien Nocera 2011-09-06 14:40:10 UTC
*** Bug 655521 has been marked as a duplicate of this bug. ***
Comment 5 Bastien Nocera 2011-09-06 14:40:15 UTC
*** Bug 655829 has been marked as a duplicate of this bug. ***
Comment 6 Bastien Nocera 2011-09-06 14:41:27 UTC
*** Bug 657241 has been marked as a duplicate of this bug. ***
Comment 7 Bastien Nocera 2011-09-06 19:50:56 UTC
*** Bug 655910 has been marked as a duplicate of this bug. ***
Comment 8 Allison Karlitskaya (desrt) 2011-09-06 20:31:04 UTC
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.
Comment 9 Allison Karlitskaya (desrt) 2011-09-18 14:07:56 UTC
I guess no news is good news from the Ubuntu guys.  I applied this patch to glib-2-30 branch as well.