gnome-settings-daemon crashes upon launch

[Barrakketh]

In Dapper, gnome-settings-daemon crashes upon logging into GNOME or manually launching it. I tried getting a stacktrace with gdb using the guide stickied on ubuntuforums.org (http://www.ubuntuforums.org/showthread.php?t=100738), but I don't get any output to copy =\

Here's the output upon launching it from a console:

The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 5933 error_code 2 request_code 116 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.)
[1143076689,000,xklavier.c:XklStartListen/] The backend does not require manual layout management - but it is provided by the application

[Sebastien Bacher (seb128)]

Thanks for your bug. Could you copy "gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd" to a comment? That might be due to an xkeyboard-config bug with compose:ralt option

[Barrakketh (barrakketh)]

 layouts = []
 model =
 options = [altwin altwin:meta_win]
 overrideSettings = true

In case you're wondering, I tried remapping the Win keys so I could use them to launch applications (I primarily use KDE and wanted to try GNOME), but every application I frequently use has a keybinding in KDE. The GNOME default only lets the Win key be used by itself (as SUPER_L)...I'm not sure whether that is a bug or not.

[Barrakketh (barrakketh)]

Here's an update. I was previously using evdev (which is broken on my mouse, see bug 36081. Short version: thumb keys are broken with evdev and mapped too high). As the bug report says, it was working in Breezy but not in Dapper. I just reconfigured my mouse in xorg.conf, and gnome-settings-daemon no longer crashes. I wouldn't consider this bug to be resolved, but hopefully this helps resolve the problem since it seemingly has to do with GNOME and X.

[Sebastien Bacher (seb128)]

evdev is known to crash gnome-settings-daemon, that's bug #27143 and should be fixed for dapper

[Stéphane Travostino (eazy87)]

Reopened in Gutsy. Today the update for gnome-control-center (1:2.19.92-0ubuntu3) shipped and broke everything.
I'm getting this error, but I'm not using evdev. I created a new user and the same error shows up.

[Rodrigo Pinheiro (ametade)]

I'm having the same error with Gutsy since I've update my system today.

:~$ gnome-settings-daemon
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 2573 error_code 2 request_code 149 minor_code 35)
  (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.)
[1190047771,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application