Package: libgtk-3-0 Version: 3.2.1-1 After updating to gtk3/gnome3 applications I experience frequent application aborts due to "XI_BadDevice (invalid Device parameter)" see below. The equivalent gtk2 applications handled the XI_BadDevice without aborting. I experienced the problem also in earlier versions of libgtk-3-0 e.g. 3.0.12-2
The XI_BadDevice seems to be caused in my case by a (not so uncommon) hardware problem which leads to disconnects and reconnects of the USB keyboard and touchpad of my Macbook pro. When using gtk2 applications the problem only lead to a short interruption during which the touchpad and keyboard was not functional. After the touchpad and keyboard get reconnected everything works normally, except for the gtk3 applications which abort (see below for error messaes) [The disconnects and reconnects also occur under OSX and are from a user point of view hardly noticable]. After updating to gnome3, the "disconnects" also abort the gnome-session i.e. I get logged out whenever this problem occurs. With many regards, Götz Gaycken (evolution:14840): Gdk-WARNING **: The program 'evolution' received an X Window System error. This probably reflects a bug in the program. The error was 'XI_BadDevice (invalid Device parameter)'. (Details: serial 63439 error_code 160 request_code 143 minor_code 48) (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.) ... ... (nm-applet:12109): Gdk-WARNING **: The program 'nm-applet' received an X Window System error. This probably reflects a bug in the program. The error was 'XI_BadDevice (invalid Device parameter)'. (Details: serial 5255 error_code 160 request_code 143 minor_code 48) (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.) gnome-session[12009]: Gdk-WARNING: The program 'gnome-session' received an X Window System error. This probably reflects a bug in the program. The error was 'XI_BadDevice (invalid Device parameter)'. (Details: serial 191 error_code 160 request_code 143 minor_code 48) (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.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
