crashes if I disconnect my drawing tablet while it is open

Bug #289762 reported by tommy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libxi (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gimp

Ubuntu 8.10
gimp 2.6.1-1ubuntu3

Steps to reproduce:
* Hotplug a wacom tablet using the new hotplugging support in intrepid (i.e. no inputdevice settings in xorg.conf, just relying on the default HAL rules in /usr/share/hal/fdi/policy/20thirdparty/10-wacom.fdi)
* Start GIMP and make a new image, draw something with the tablet which should work fine
* turn off / unplug the tablet
* use your mouse to move the cursor from outside of the GIMP window to inside it

expected > GIMP acts as it would normally if the tablet was not connected

actual result > GIMP crashes, no error dialog or anything

running GIMP from a terminal gives this message:

The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDevice, invalid or uninitialized input device'.
  (Details: serial 314305 error_code 168 request_code 148 minor_code 30)
  (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.)

(script-fu:1988): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02)
     Subsystem: Giga-byte Technology Device [1458:5000]
01:00.0 VGA compatible controller [0300]: nVidia Corporation G80 [GeForce 8800 GTS] [10de:0193] (rev a2)
     Subsystem: nVidia Corporation Device [10de:0421]

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gimp:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

there is no need to specify the version you are using in the title, that creates extra work and confusion

Revision history for this message
tommy (yobbobandana) wrote :

I installed gimp-dbg and ran gdb as per the instructions at https://wiki.ubuntu.com/Backtrace. Here is the output.

It doesn't seem to have any extra info. Are there more commands I could try, or should I install some extra -dbg packages?

I forgot to add I'm running the amd64 version of ubuntu.

Revision history for this message
tommy (yobbobandana) wrote :

I installed libgtk2.0.0-dbg (don't know if that was necessary) and got a more meaningful looking result by setting a breakpoint at gdk_x_error and running with "run --sync". Here it is.

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

the issue seems to be a libxi rather

Changed in gimp:
status: Incomplete → New
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi yobbobandana,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in libxi:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in libxi:
status: Incomplete → Invalid
Revision history for this message
tommy (yobbobandana) wrote :

Erm, this bug is 4 days old.

Here is Xorg.0.log (just after crashing GIMP via the method outlined above).

I also found that I can crash Inkscape via the same method of unplugging the tablet, although it doesn't crash until I click inside the window with the mouse.

Revision history for this message
tommy (yobbobandana) wrote :

lspci -vvnn

Changed in libxi:
status: Invalid → New
Bryce Harrington (bryce)
Changed in libxi:
status: New → Confirmed
Bryce Harrington (bryce)
description: updated
Revision history for this message
Tynach (tynach2) wrote :

I just needed to comment on this... I have a Wacom tablet that has a slight loose connection in the cord, so it often disconnects. I find Gimp crashing on me A LOT.

It's making Gimp unusable right now, and I have to boot up Vista and use Photoshop.

Using Gimp 2.6.6 on Ubuntu 9.04, x86-64 version. My system is entirely updated.

The tablet is a Graphire 3.

I have not run a backtrace, but I imagine it would yield the same results, as it is precisely the same problem.

Bryce Harrington (bryce)
tags: added: intrepid
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Please try on lucid (livecd or otherwise), I haven't been able to reproduce it there.

Changed in libxi (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

closing, should be fixed in lucid.

Changed in libxi (Ubuntu):
status: Incomplete → Fix Released
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.