Bug#372873: backtrace

[Wojtek Zabolotny]

>           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.)
>                 [1150103899,000,xklavier.c:XklStartListen/]     The
>                 backend does not require manual layout management -
> but
>                 it is provided by the application


> Can you provide us with a backtrace, as described in the error message?

I'm sorry, but I'm not able to set the desired breakpoint. Probably it
requires a debug version of gnome-settings-daemon or some libraries:

$ gdb gnome-settings-daemon
GNU gdb 6.4-debian
Copyright 2005 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 "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) set args --sync
(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y

Breakpoint 1 (gdk_x_error) pending.
(gdb) run
Starting program: /usr/bin/gnome-settings-daemon --sync
(no debugging symbols found)
(no debugging symbols found)
[...]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

[New Thread -1227056208 (LWP 9264)]
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 5877 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.)
[1150192889,000,xklavier.c:XklStartListen/]     The backend does not
require manual layout management - but it is provided by the application
Program exited with code 01.

That's all - program finished, no way to get bt :-(
-- 
Regards, Wojtek