Steps to reproduce:
1. startx (I'm using fvwm)
2. execute /usr/libexec/gnome-settings-daemon
3. it crashes


Stack trace:
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/libexec/gnome-settings-daemon 
[Thread debugging using libthread_db enabled]
[New Thread -1224194384 (LWP 12775)]

** (gnome-settings-daemon:12775): WARNING **: The system configuration changed - but we remain silent

[New Thread -1225573472 (LWP 12780)]
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 1506 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.)
[1152292032,000,xklavier.c:XklStartListen/]     The backend does not require manual layout management - but it is provided by the application
Program exited with code 01.
(gdb) thread apply all bt
(gdb) run
Starting program: /usr/libexec/gnome-settings-daemon 
[Thread debugging using libthread_db enabled]
[New Thread -1224653136 (LWP 12781)]

** (gnome-settings-daemon:12781): WARNING **: The system configuration changed - but we remain silent

[New Thread -1226032224 (LWP 12784)]
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 2250 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.)
[1152292066,000,xklavier.c:XklStartListen/]     The backend does not require manual layout management - but it is provided by the application
Program exited with code 01.
(gdb) bt
No stack.
(gdb) quit


Other information:
here: http://bugzilla.gnome.org/show_bug.cgi?id=342980 I was asked to fill a new bug, so here it is:

X is run with startx, in ~/.xinitrc, I juste have:
xset m 7/10 1
exec fvwm

and X is launch with "-nolisten tcp -br"

I have :
        Option      "XkbRules"  "xorg"
        Option      "XkbModel"  "pc105"
        Option      "XkbLayout" "fr"

in xorg.conf so I suppose this means I have XKB enabled?

I'm using gentoo, and all the system is compiled with :
CFLAGS="-O2 -march=athlon-xp -pipe"
CXXFLAGS="-O2 -march=athlon-xp -pipe"

I rebuild all gnome things with the use flag 'debug', which add -g to CFLAGS. I also add "splitdebug" in FEATURES for these packages.

( With splitdebug enabled, Portage will still strip the binaries installed in the system. But before doing that, all the useful debug information is copied to a ".debug" file, which is then installed inside /usr/lib/debug (the complete name of the file would be given by appending to that the path where the file is actually installed). The path to that file is then saved in the original file inside an ELF section called ".gnu_debuglink", so that gdb knows which file to load the symbols from )



The only other thing I've noticed when trying to launch gnome-settings-daemon, is
that firefox is consuming about 99%  of the CPU, until 2 or 3 minutes after the
try, (and I only see the firefox window, not its content)