gnome-settings-daemon crashes with BadValue X11 Error

Bug #140491 reported by Peter Clifton
2
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-control-center

Running:
gdb --args gnome-settings-daemon --sync

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 1807 error_code 2 request_code 146 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.)
[1190052505,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
Program exited with code 01.

Setting the breakpoint on gdk_x_error, I've got the partial backtrace:

Breakpoint 2, gdk_x_error (display=0x808f100, error=0xbf90b358)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
614 /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c: No such file or directory.
        in /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c
(gdb) bt
#0 gdk_x_error (display=0x808f100, error=0xbf90b358)
    at /build/buildd/gtk+2.0-2.12.0/gdk/x11/gdkmain-x11.c:614
#1 0x45fdd655 in bonobo_x_error_handler (display=0x808f100, error=0xbf90b358)
    at bonobo-ui-main.c:58
#2 0x4e031f50 in xkl_process_error () from /usr/lib/libxklavier.so.11
#3 0x4d817c4a in _XError (dpy=0x808f100, rep=0xbf90b454)
    at ../../src/XlibInt.c:2907
#4 0x4d819714 in _XReply (dpy=0x808f100, rep=0xbf90b454, extra=0, discard=1)
    at ../../src/XlibInt.c:1833
#5 0x4daa684f in XChangeDeviceControl (dpy=0x808f100, dev=0x80f5438,
    control=1, d=0xbf90b4dc) at ../../src/XChgDCtl.c:206
#6 0x0805dbed in ?? ()
#7 0x0808f100 in ?? ()
#8 0x080f5438 in ?? ()
#9 0x00000001 in ?? ()
#10 0xbf90b4dc in ?? ()
#11 0x080fa390 in ?? ()
#12 0xbf90b4f8 in ?? ()
#13 0x00000001 in ?? ()
#14 0x00000001 in ?? ()
#15 0x00000014 in ?? ()
#16 0x00000000 in ?? ()

And:

 thread 2
[Switching to thread 2 (Thread -1216083056 (LWP 22315))]#0 0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x4d7b11fb in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb79f50bd in child_watch_helper_thread (data=0x0)
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c:3899
#3 0xb7a175af in g_thread_create_proxy (data=0x80c3830)
    at /build/buildd/glib2.0-2.14.1/glib/gthread.c:635
#4 0x4d7aa46b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0x4d6ff6be in clone () from /lib/tls/i686/cmov/libc.so.6

I'm in the process of trying to figure out what dbgsym packages to install for a full back-trace.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gnome-control-center:
importance: Undecided → Medium
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.