After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 663948 - Applications abort with XI_BadDevice
Applications abort with XI_BadDevice
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: .General
unspecified
Other Linux
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-11-13 07:18 UTC by Josselin Mouette
Modified: 2011-12-30 04:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Stack track of x-session-manager which was stopped in gdk_x_error. (2.85 KB, text/plain)
2011-11-20 21:11 UTC, Goetz Gaycken
Details
kernel message at the time of the error (1.66 KB, application/octet-stream)
2011-11-20 21:15 UTC, Goetz Gaycken
Details

Description Josselin Mouette 2011-11-13 07:18:34 UTC
I have received this bug on the Debian BTS; I found several occurrences of it on other distros:
http://bugs.debian.org/648562
https://bugzilla.redhat.com/show_bug.cgi?id=728044
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/882956
https://bugs.archlinux.org/task/24096

I’m forwarding this here to track all those bugs, because so far gtk+ has been blamed.

The symptoms are that applications using gtk3 (including gnome-session) can exit suddenly in some cases:
 - suspend/resume cycle for some people,
 - dysfunctional keyboard for one occurrence.

Errors look like this:
(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)
Comment 1 Matthias Clasen 2011-11-15 05:29:42 UTC
Still waiting for a usable stacktrace from where that X error happens.
Comment 2 Goetz Gaycken 2011-11-20 21:11:59 UTC
Created attachment 201771 [details]
Stack track of x-session-manager which was stopped in gdk_x_error.
Comment 3 Goetz Gaycken 2011-11-20 21:15:14 UTC
Created attachment 201772 [details]
kernel message at the time of the error

In case it helps, I also attached the kernel messages which appeared at the
time of the GDK error. Though I don't know the exact time when the gdk_x_error was catched.
Comment 4 Goetz Gaycken 2011-11-20 21:18:28 UTC
Hello,

unfortunately I don't know how to trigger the cause of the problem. This time it took a few hours. I first attached the debugger to evolution, then gnome-shell and set a break point in gdk_x_error. But the session got always killed before the error was trapped. Finally I attached the debugger to the x-session-manager. If You have any suggestions what I should do instead, let me know.

Cheers,
  Götz Gaycken
Comment 5 Goetz Gaycken 2011-11-20 21:47:51 UTC
... and in gdb I tried "finish" but that terminated the x-session-manager.
Comment 6 Matthias Clasen 2011-11-30 05:20:21 UTC
Thanks for that stacktrace. I've now pushed a patch that might help, would be great if you could test that.
Comment 7 Josselin Mouette 2011-11-30 08:55:29 UTC
Goetz, this is the patch: http://git.gnome.org/browse/gtk+/commit/?id=9b967ab8aff46b79494d75a3129fa8780545ecd1

I’ll push it in gtk+3.0/unstable, but it would be nice if you could test it beforehand.
Comment 8 Goetz Gaycken 2011-12-04 22:48:46 UTC
Thank You very much for the patch !

I applied the patch and it seems to have solved the problem. I had a few
disconnects of the touchpad/keyboard since then, but no aborts of any of
the gtk3 applications.

Cheers,
  Götz
Comment 9 Matthias Clasen 2011-12-30 04:57:45 UTC
Considering this fixed, then.