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 169304 - Selecting tools crashes the GIMP
Selecting tools crashes the GIMP
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: Tools
2.2.x
Other Linux
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-03-05 16:58 UTC by Rik Meijer
Modified: 2008-01-15 12:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rik Meijer 2005-03-05 16:58:12 UTC
Distribution/Version: Fedora Core 3

1. Start GIMP
2. Select one of the following tools:
 - Path editor
 - Color picker
 - Magnifier
 - Move
 - Crop/Resize
 - Rotate selection/layer
 - Scale
 - Shear
 - Change perspective
 - Flip layer/selection
 - Fill color/pattern
 - Draw ink
 - Pattern paint
 - Blur/Sharpen
 - Dodge/Burn strokes
3. See error message appear in console:
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 34593 error_code 8 request_code 56 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:7059): LibGimpBase-WARNING **: script-fu: wire_read(): error

*** I guess the number in "script-fu:7059" represents a line number in the
script. Also it varies depending on the tool selected.

It does not matter if I select a tool via the toolpanel or via a keyboard
shortcut: results are the same.

I believe it started happening after updating the GIMP to version 2.2.3.
Upgrading to 2.2.4 didn't solve the problem.

GIMP related installed packages:
- gimp-print-plugin-4.2.7-2
- xsane-gimp-0.92-13
- gimp-2.2.4-0.fc3.1
- gimp-print-4.2.7-2
- gimp-print-utils-4.2.7-2
- gimp-gap-2.0.2-2
- gimp-data-extras-1.2.0-12
- gimp-print-cups-4.2.7-2
- gimp-help-2-0.1.0.7.0.fc3.1
Comment 1 Sven Neumann 2005-03-05 17:28:13 UTC
Your X server or your GTK+ library has a bug. This is not a GIMP problem, it
works for everyone else.
Comment 2 Rik Meijer 2005-03-07 20:40:25 UTC
Changing the theme in Fedora from bluecurve to another fixed it somehow
Comment 3 Sven Neumann 2005-03-07 21:02:45 UTC
I have no idea where bluecurve is hosted. There isn't a product in gnome
bugzilla for it, is there?
Comment 4 Rik Meijer 2005-03-07 21:09:02 UTC
Nope it's the default theme for Fedora Core , but it might be useful for anyone
who gets the same error.
Comment 5 weskaggs 2005-03-07 22:40:23 UTC
BlueCurve is the default theme that RedHat uses (and hence Fedora).  If there
was a problem with it in general, we would probably be hearing a lot about it. 
So it's not clear what went wrong on your system.
Comment 6 Rik Meijer 2005-03-07 23:05:11 UTC
Perhaps it had something to do with an upgrade of GTK+-1.2.10-33 or
gtk2-2.6.4-1.1. I also started to have problems with openoffice
(https://bugzilla.redhat.com/beta/show_bug.cgi?id=144607) but I'm really not
sure if that's in any way related.
Comment 7 Samuel Stringham 2005-08-01 01:27:02 UTC
*** Bug 154867 has been marked as a duplicate of this bug. ***