GNOME Bugzilla – Bug 143292
gnome-settings-daemon crashes at startup
Last modified: 2006-05-22 13:11:34 UTC
Description of Problem: Using the 2004-05-27 'snapshot' of Debian Unstable, at GNOME startup, gnome-settings-daemon fails to start and throws up a crash dialog (which is totally uninformative). Trying to start it by hand causes it to ponder for about 30 seconds then it emits the following results: ------------------- $ /usr/lib/control-center/gnome-settings-daemon ** (gnome-settings-daemon:8557): WARNING **: Could not activate the XKB configuration The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 112 error_code 1 request_code 0 minor_code 0) (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.) ------------------- The selected GTK+ theme, font settings, etc. are applied when it starts, and reset to the default as it crashes. Steps to reproduce the problem: 1. Upgrade to Debian Unstable 2. Start X with a Gnome session. How often does this happen? Every time. Additional Information: $ gnome-session --version Gnome gnome-session 2.6.1 $ /usr/lib/control-center/gnome-settings-daemon --version Gnome gnome-settings-daemon 2.6.1 steer@bubbles:~$ dpkg --list|grep xserver ii xserver-common 4.3.0.dfsg.1-2 files and utilities common to all X servers ii xserver-xfree8 4.3.0.dfsg.1-2 the XFree86 X server I'll supply you with more information if needed.
I suspect this is related to http://lists.debian.org/debian-x/2004/05/msg00693.html However, we should not generating X failures under any circumstances, all calls to raw X need error handlers in place. Could someone please follow the instructions provided by the x abort and supply a back trace so that can see where the unprotected call was made ? Thanks
Backtrace here : ** (gnome-settings-daemon:11569): WARNING **: Could not activate the XKB configuration Program received signal SIGSEGV, Segmentation fault.
+ Trace 46991
Thread 1089641536 (LWP 11569)
I can attach a bugged keyboard file if you want to reproduce the bug... (the patch if the previous comment is enough to reproduce too)
Bug 146140 may be a duplicate.
is this still valid, Roland?
No feedback. Closing.