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 333448 - Multiple crashes when toolbox is moved to another screen
Multiple crashes when toolbox is moved to another screen
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: User Interface
git master
Other All
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-03-05 08:37 UTC by Ville Pätsi
Modified: 2006-03-07 09:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ville Pätsi 2006-03-05 08:37:10 UTC 
Steps to reproduce:
Selecting display tab in preferences:

The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 153819 error_code 8 request_code 56 minor_code 0)


Selecting crop tool:

The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 188607 error_code 8 request_code 56 minor_code 0)


Stack trace:


Other information:
Comment 1 weskaggs 2006-03-05 20:21:06 UTC 
Since this is an X error, it might be helpful for you to tell us what OS, what version of X11, and what window manager you are using.
Comment 2 Ville Pätsi 2006-03-05 20:56:23 UTC 
Fedora Core 4, xorg 6.8.2 (Fedora patch level 37), and sawfish 1.3
Comment 3 Michael Natterer 2006-03-06 14:23:32 UTC 
The exact gtk version and the dockables that are attached to the
toolbox are probably more relevant.
Comment 4 Ville Pätsi 2006-03-06 14:37:41 UTC 
GTK+ 2.8.11 (gtk-2-8 built 2006-01-20). 

Toolbox only has the tool options docked.
Comment 5 Simon Budig 2006-03-06 15:45:36 UTC 
Do both screens have the same bitdepth? A friend just told me about a problem when moving image views from a 24bit screen to a 16 bit screen:

 The program 'gimp' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'BadGC (invalid GC parameter)'.

I have to come back to this to investigate this in more detail to be able to give a better description and backtrace. However, in this case I guess that the Graphic Contexts are not updated when moving the image window to a different screen.
Comment 6 Michael Natterer 2006-03-06 21:08:27 UTC 
Ville, would you run gimp with --sync --g-fatal-warnings and attach
a backtrace of the BadMatch?
Comment 7 Ville Pätsi 2006-03-06 21:41:22 UTC 
This is for the display preferences:

+ Trace 66739

  • #0 gdk_x_error
    from /home/drc/next/lib/libgdk-x11-2.0.so.0
  • #1 _XError
    from /usr/X11R6/lib/libX11.so.6
  • #2 _XReply
    from /usr/X11R6/lib/libX11.so.6
  • #3 XSync
    from /usr/X11R6/lib/libX11.so.6
  • #4 XSync
    from /usr/X11R6/lib/libX11.so.6
  • #5 XCopyArea
    from /usr/X11R6/lib/libX11.so.6
  • #6 gdk_x11_draw_drawable
    from /home/drc/next/lib/libgdk-x11-2.0.so.0
  • #7 gdk_draw_drawable
    from /home/drc/next/lib/libgdk-x11-2.0.so.0
  • #8 gdk_pixmap_draw_drawable
    from /home/drc/next/lib/libgdk-x11-2.0.so.0
  • #9 gdk_draw_drawable
    from /home/drc/next/lib/libgdk-x11-2.0.so.0
  • #10 gdk_window_draw_drawable
    from /home/drc/next/lib/libgdk-x11-2.0.so.0
  • #11 gdk_draw_drawable
    from /home/drc/next/lib/libgdk-x11-2.0.so.0
  • #12 bluecurve_rc_style_register_type
    from /home/drc/next/lib/gtk-2.0/2.4.0/engines/libbluecurve.so
  • #13 gtk_paint_option
    from /home/drc/next/lib/libgtk-x11-2.0.so.0
  • #14 gtk_radio_button_draw_indicator
    from /home/drc/next/lib/libgtk-x11-2.0.so.0 

(Didn't know where to cut the trace so picked a random point)
Comment 8 Simon Budig 2006-03-06 23:02:28 UTC 
Hmm, thats deep inside GTK+. Can you try with the default theme instead of bluecurve? And can you provide the stack trace to at least a point within the GIMP, so that it is recognizable in what part of the GIMP the GTK+ originate?
Comment 9 Ville Pätsi 2006-03-07 07:25:15 UTC 
No crash with the default theme. I guess bluecurve is to blame.
Comment 10 Sven Neumann 2006-03-07 07:28:56 UTC 
Yes, this is most definitely a bug in the theme engine. Can we reassign this report or close it as NOTGNOME in case that the theme engine is not available as a product in this bug-tracker?
Comment 11 Ville Pätsi 2006-03-07 07:50:41 UTC 
Go right ahead.
Comment 12 Sven Neumann 2006-03-07 08:10:53 UTC 
Ville, I am asking you to do this. After all it is you who opened the bug-report on the wrong product.