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 591137 - Crash after removing graphic tablet
Crash after removing graphic tablet
Status: RESOLVED DUPLICATE of bug 575767
Product: gtk+
Classification: Platform
Component: Input Methods
2.17.x
Other All
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-08-08 10:49 UTC by Hernando Torque
Modified: 2009-08-08 12:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
thread apply all bt (3.77 KB, text/plain)
2009-08-08 10:53 UTC, Hernando Torque
Details
thread apply all bt full (19.19 KB, text/plain)
2009-08-08 10:53 UTC, Hernando Torque
Details

Description Hernando Torque 2009-08-08 10:49:57 UTC
Steps to reproduce:
1. Open Gimp with a graphic tablet attached (in my case a Wacom Bamboo)
2. Unplug the graphic tablet
3. Trying to open a new file crashes the application

Any access to the unplugged device will cause the crash.

Stack trace:
  • #0 gdk_x_error
    at /build/buildd/gtk+2.0-2.17.6/gdk/x11/gdkmain-x11.c line 439
  • #1 _XError
    at ../../src/XlibInt.c line 2924
  • #2 _XReply
    at ../../src/xcb_io.c line 506
  • #3 XQueryDeviceState
    at ../../src/XQueryDv.c line 87
  • #4 gdk_input_check_proximity
    at /build/buildd/gtk+2.0-2.17.6/gdk/x11/gdkinput-xfree.c line 93
  • #5 _gdk_input_crossing_event
    at /build/buildd/gtk+2.0-2.17.6/gdk/x11/gdkinput-xfree.c line 150
  • #6 send_crossing_event
    at /build/buildd/gtk+2.0-2.17.6/gdk/gdkwindow.c line 8522
  • #7 proxy_pointer_event
    at /build/buildd/gtk+2.0-2.17.6/gdk/gdkwindow.c line 9104
  • #8 _gdk_windowing_got_event
    at /build/buildd/gtk+2.0-2.17.6/gdk/gdkwindow.c line 9485
  • #9 _gdk_events_queue
    at /build/buildd/gtk+2.0-2.17.6/gdk/x11/gdkevents-x11.c line 2315
  • #10 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.17.6/gdk/x11/gdkevents-x11.c line 2373
  • #11 g_main_dispatch
    at /build/buildd/glib2.0-2.21.4/glib/gmain.c line 1960
  • #12 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.21.4/glib/gmain.c line 2513
  • #13 g_main_context_iterate
    at /build/buildd/glib2.0-2.21.4/glib/gmain.c line 2591
  • #14 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.21.4/glib/gmain.c line 2799
  • #15 app_run
  • #16 main

Other information:
Comment 1 Hernando Torque 2009-08-08 10:53:17 UTC
Created attachment 140188 [details]
thread apply all bt
Comment 2 Hernando Torque 2009-08-08 10:53:58 UTC
Created attachment 140189 [details]
thread apply all bt full
Comment 3 Hernando Torque 2009-08-08 10:55:27 UTC
Forgot to add the command line output:

Gdk-ERROR **: The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 38138 error_code 146 request_code 140 minor_code 13)
  (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.)
aborting...

(script-fu:3282): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
Comment 4 Sven Neumann 2009-08-08 11:50:48 UTC
As you can see in the stack-trace, there is no GIMP code involved here. Please reassign to GTK+ and specify the GTK+ version and your operating system.
Comment 5 Hernando Torque 2009-08-08 12:19:02 UTC
Oops, you're right. I'm afraid I don't have the permissions to reassign?

I'm using Ubuntu 9.10 Alpha 3 with GTK+ version 2.17.6.
Comment 6 Martin Nordholts 2009-08-08 12:20:32 UTC
Reassigning.
Comment 7 Hernando Torque 2009-08-08 12:39:05 UTC

*** This bug has been marked as a duplicate of 575767 ***