| 2015-05-13 06:47:06 |
pe |
description |
I started inkscape yesterday, suspend my laptop overnight, suspended it again several times without using inkscape (though it was running).
When I wanted to resume my inkscape work, it crashed on the first key I stroke, with the following message in the terminal I started it from:
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 1637195 error_code 129 request_code 131 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.)
I'm sorry I can't provide more information. I have no particular plugins installed, and I was editing an svg file automatically generated by a program, and then edited and saved with inkscape. |
I started inkscape yesterday, suspend my laptop overnight, suspended it again several times without using inkscape (though it was running).
When I wanted to resume my inkscape work, it crashed on the first key I stroke, with the following message in the terminal I started it from:
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 1637195 error_code 129 request_code 131 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.)
I'm sorry I can't provide more information. I have no particular plugins installed, and I was editing an svg file automatically generated by a program, and then edited and saved with inkscape.
I'm using debian testing (as of May 13, 2015), 64 bits, kernel 4.0.0-rc6, and dwm as my window manager. When I start Inkscape from the terminal, I don't see any complaint message about any missing library or module (in fact inkscape normally writes nothing in the terminal).
Resuming from suspend sometimes causes systemd services to be restarted in a strange order: some services depending on not mounting partitions are sometimes ran even though the partitions are mounted.
I've not yet investigated nor tried to fix this problem, and I'm not sure it is of any relevance to this inkscape bug. |
|
