XI_BadDevice - Crash after undocking Lenovo laptop

Likely the same underlying issue as in
 Bug #474954 in Inkscape: “crashes when USB input device is disconnected”
 <https://bugs.launchpad.net/inkscape/+bug/474954>
See also the backtrace in other duplicate bug #818543, comment #5.

(backtrace formatted in LO, seriously? ;-) )

Sorry about that.

Looks like you're correct, I just had Inkscape running and disconnected the USB mouse attached to my docking station and got it to crash by clicking. To add to that though, if I have the text tool selected before hand, I can click on text and edit it fine, but when I click on a rectangle, that's when it crashes.

GNU gdb (GDB) Fedora (7.3.1-45.fc15)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/inkscape...(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install inkscape-0.48.1-4.fc15.x86_64
(gdb) run
Starting program: /usr/bin/inkscape
[Thread debugging using libthread_db enabled]

Gdk-ERROR **: The program 'inkscape' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 55598 error_code 149 request_code 141 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...

Program received signal SIGABRT, Aborted.
0x00000032bf4352d5 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x00000032bf4352d5 in raise () from /lib64/libc.so.6
#1 0x00000032bf436beb in abort () from /lib64/libc.so.6
#2 0x00000032c104b5ee in g_logv () from /lib64/libglib-2.0.so.0
#3 0x00000032c104b682 in g_log () from /lib64/libglib-2.0.so.0
#4 0x000000311886ab7b in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
#5 0x00000032c2c4810f in _XError () from /usr/lib64/libX11.so.6
#6 0x00000032c2c44f91 in ?? () from /usr/lib64/libX11.so.6
#7 0x00000032c2c45ee7 in _XReply () from /usr/lib64/libX11.so.6
#8 0x00000032c4c0573d in XGrabDevice () from /usr/lib64/libXi.so.6
#9 0x000000311888195a in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
#10 0x000000311886addf in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
#11 0x000000311884a0fc in gdk_pointer_grab ()
   from /usr/lib64/libgdk-x11-2.0.so.0
#12 0x000000000078c0c9 in sp_canvas_item_grab(SPCanvasItem*, unsigned int, _GdkCursor*, unsigned int) ()
#13 0x0000000000b1f5af in ?? ()
#14 0x0000000000669722 in sp_event_context_virtual_item_handler(SPEventContext*, SPItem*, _GdkEvent*) ()
#15 0x000000000080eb34 in sp_marshal_INT__POINTER_POINTER ()
#16 0x00000032c1c0e34e in g_closure_invoke () from /lib64/libgobject-2.0.so.0
#17 0x00000032c1c1f200 in ?? () from /lib64/libgobject-2.0.so.0
#18 0x00000032c1c2878b in g_signal_emit_valist ()
   from /lib64/libgobject-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#19 0x0000003118ef0695 in gtk_signal_emit ()
   from...

<off-topic>
Matt Reid wrote:
> Sorry about that.

I forgot to add a 'SCNR' ;)
</off-topic>

Would you agree to link your report as duplicate to bug #474954, to allow easier tracking the issue in a single report?

Sure, I'm fine with that.