Comment 7 for bug 19784

(In reply to comment #4)
> how do you know it crashes? Could you attach gdb to it when it try to restart or
> start an instance with gdb?

I have the exact same problem: After modifying the system keyboard properties, window decoration starts going crazy until
after a while, I get the message "gnome-setting-daemon couldn't start" (that's the gist of it). When running gnome-
settings-daemon in a terminal, I get the following:

Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
                  Ignoring extra symbols
Warning: No symbols defined for <SYRQ> (keycode 92)
[...]
Warning: No symbols defined for <I7F> (keycode 255)
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 1580 error_code 2 request_code 145 minor_code 9)
  (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.)
[1129906626,000,xklavier.c:XklStartListen/] The backend does not require manual layout management - but it is provided
by the application

Complete output attached. I guess this is not a segfault so a gdb backtrace won't be available.