GNOME Bugzilla – Bug 577136
Keyboard initialization (libkeyboard.so: gsd_keyboard_xkb_init) failed
Last modified: 2009-03-29 17:34:36 UTC
Steps to reproduce: 1. start gnome-settings-daemon $ /usr/libexec/gnome-settings-daemon --debug --no-daemon 2. Daemon failed with backtrace indicating keyboard init problem. $ gnome-settings-daemon: xcb_xlib.c:73: xcb_xlib_lock: Assertion `!c->xlib.lock' failed. 3. xcb lock workaround doesn't really helps $ LIBXCB_ALLOW_SLOPPY_LOCK=1 /usr/libexec/gnome-settings-daemon --debug --no-daemon gives high CPU load. But daemon started fine and settings restored correctly. Stack trace: ** (gnome-settings-daemon:27359): DEBUG: GsdKeyboardPlugin initializing ** (gnome-settings-daemon:27359): DEBUG: Activating keyboard plugin ** (gnome-settings-daemon:27359): DEBUG: Starting keyboard manager Gdk-ERROR **: The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadClass, invalid event class'. (Details: serial 169 error_code 184 request_code 148 minor_code 6) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... Locking assertion failure. Backtrace: #0 /usr/lib/libxcb-xlib.so.0 [0xb75ab857] #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb75ab90e] #2 /usr/lib/libX11.so.6 [0xb75ef9f6] #3 /usr/lib/libX11.so.6(XUngrabPointer+0x25) [0xb75e64a5] #4 /usr/lib/libgdk-x11-2.0.so.0(gdk_display_pointer_ungrab+0x84) [0xb7ac2384] #5 /usr/lib/libgdk-x11-2.0.so.0(gdk_pointer_ungrab+0x1a) [0xb7a9d9ca] #6 /usr/lib/gtk-2.0/modules/libgnomebreakpad.so [0xb7ee470f] #7 [0xb7ef0400] #8 /usr/lib/libglib-2.0.so.0(g_log+0x29) [0xb6e4def9] #9 /usr/lib/libgdk-x11-2.0.so.0 [0xb7adcd24] #10 /usr/lib/libxklavier.so.12(xkl_process_error+0xe4) [0xb5f76124] #11 /usr/lib/libX11.so.6(_XError+0xd2) [0xb75e8dd2] #12 /usr/lib/libX11.so.6 [0xb75f0346] #13 /usr/lib/libX11.so.6(_XReply+0x15c) [0xb75f06ec] #14 /usr/lib/libX11.so.6(_XGetWindowAttributes+0xc8) [0xb75cff98] #15 /usr/lib/libX11.so.6(XGetWindowAttributes+0x42) [0xb75d00e2] #16 /usr/lib/libxklavier.so.12(xkl_engine_select_input_merging+0x51) [0xb5f74f51] #17 /usr/lib/libxklavier.so.12(xkl_engine_resume_listen+0x81) [0xb5f75001] #18 /usr/lib/libxklavier.so.12(xkl_engine_start_listen+0x36) [0xb5f756c6] #19 /usr/lib/gnome-settings-daemon-2.0/libkeyboard.so(gsd_keyboard_xkb_init+0x2f6) [0xb5facf06] gnome-settings-daemon: xcb_xlib.c:73: xcb_xlib_lock: Assertion `!c->xlib.lock' failed. [1238279995,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationMultiple segmentation faults occurred; can't display error dialog Other information: Setting daemon built with following options: alsa debug gstreamer libnotify -esd -pulseaudio
What are the exact versions of g-s-d, libxklavier, and of the X.org server? Certain 2.24 versions had problems with X servers that don't support hotplugging of input devices. Might also be a bug in libxklavier, though.
Thanks for valuable comment, the problem solved by updating xorg-server to 1.5.3-r5; Here are the version list with which problem may be repeated: g-s-d: 2.24.1-r1; libxklavier: 3.8; xorg-server: 1.3.0.0-r6; Is it possible that the problem caused by x11-misc/xkeyboard-config-1.1, x11-libs/libxkbfile-1.0.4 or x11-drivers/xf86-input-keyboard-1.1.1?
It's very likely that you hit bug 562977. *** This bug has been marked as a duplicate of 562977 ***