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 448724 - Gimp crashes when using a Painbrush tool or similar
Gimp crashes when using a Painbrush tool or similar
Status: RESOLVED DUPLICATE of bug 445376
Product: GIMP
Classification: Other
Component: Script-Fu
2.3.x
Other All
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-06-18 10:00 UTC by Ulrike Jahnke-Soltau
Modified: 2008-01-15 14:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ulrike Jahnke-Soltau 2007-06-18 10:00:22 UTC
Steps to reproduce:
1. File, New, ok, 
2. select a pencil, paintbrush or similar
3. try to paint, and it crashes sooner or later, mostly sooner, with the following message:


Stack trace:

xxxxx@xxxxx ~/projekte/bilder $ gimp
This is a development version of GIMP.  Debug messages may appear here.

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 26493 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.)
xxxxx@xxxxx ~/projekte/bilder $
(script-fu:8455): LibGimpBase-WARNING **: script-fu: wire_read(): error



Other information:
OS: Linux x86-64-2.6.21-gentoo
Comment 1 Sven Neumann 2007-06-18 10:44:27 UTC
Your copy of XLib is broken.

*** This bug has been marked as a duplicate of 445376 ***
Comment 2 Ulrike Jahnke-Soltau 2007-06-18 19:19:05 UTC
The Bug that obviously was a duplicate used XLib 1.12

I updated to XLib 1.14, it got me the same crash with slighly different addresses.

(script-fu:7168): LibGimpBase-WARNING **: script-fu: wire_read(): error

Which XLib do you think is appropriate?

Comment 3 Simon Budig 2007-06-18 20:56:47 UTC
This bug has been fixed upstream a week ago or something. So any libx11 version released earlier should be considered suspicious.

I am closing this bug again, since it is pretty likely that this still is a buggy version.

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