Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#7407 - gimp-2.2.15 crashes with X Window System Error using Eraser tool
Attached to Project:
Arch Linux
Opened by Michael Fiano (musifreq) - Saturday, 09 June 2007, 22:34 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 10 June 2007, 08:22 GMT
Opened by Michael Fiano (musifreq) - Saturday, 09 June 2007, 22:34 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 10 June 2007, 08:22 GMT
|
DetailsWhen clicking and dragging with the eraser tool, gimp crashes immediately everytime.
[axion@axion|~>pacman -Q|grep gimp gimp 2.2.15-1 [axion@axion|~>gimp The program 'gimp' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 177723 error_code 3 request_code 39 minor_code 0) (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:23504): LibGimpBase-WARNING **: script-fu: wire_read(): error [axion@axion|~>rm -rf ~/.gimp-2.2/ [axion@axion|~>gimp The program 'gimp' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 199725 error_code 3 request_code 39 minor_code 0) (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:23684): LibGimpBase-WARNING **: script-fu: wire_read(): error |
This task depends upon