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 157541 - gnome-panel crashes when there are too many background images added in the background prefs.
gnome-panel crashes when there are too many background images added in the ba...
Status: RESOLVED DUPLICATE of bug 128317
Product: gnome-panel
Classification: Other
Component: general
2.8.x
Other Linux
: High major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-11-06 20:15 UTC by Zach J. Elko
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Zach J. Elko 2004-11-06 20:15:52 UTC
1. Add at least over 60 pictures to the background selecter.
2. Change your background

NOTE: I noticed some sketchy behavior with these tests when Gnome tried to
tile/scale the images to your screen. If you have over 60 added, and it doesn't
crash, exit out, go back in, and try it again. Also, try different sized
pictures as well. I could not make it crash with exactly 60 pictures added, no
matter what I did. I only tested down to 59, and that didn't crash either.

The following is the error message displayed if you ran gnome-terminal from a
command shell when this bug occured:

The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 24035 error_code 13 request_code 62 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.)

Also, the error dialogue: "I've detected another panel running and will now
exit" refuses to go away. If you hit OK, it comes back up.
Comment 1 Zach J. Elko 2004-11-07 05:48:40 UTC
I'm sorry to report it has been randomly crashing now with the list at 59. I see
no distinct pattern anymore for why it crashes. It didn't crash at all for 5
minutes of switching backgrounds, and I come back to it for the purpose of
actually changing my background, and it crashed twice. The information provided
thus far should be enough to address this, as I don't want to test this 60 more
times...
Comment 2 Zach J. Elko 2004-11-09 02:28:15 UTC
This was tested on Arch .7, kernel 2.6.9, with the gnome-panel being either
transparent or solid, and auto-hide off.
Comment 3 Zach J. Elko 2004-11-09 02:41:08 UTC
Here is a backtrace from gdk_x_error() on to the end.

  • #33 gdk_x_error
    from /usr/lib/libgdk-x11-2.0.so.0
  • #34 bonobo_x_error_handler
    from /opt/gnome/lib/libbonoboui-2.so.0
  • #35 _XError
    from /usr/X11R6/lib/libX11.so.6
  • #36 _XReply
    from /usr/X11R6/lib/libX11.so.6
  • #37 XSync
    from /usr/X11R6/lib/libX11.so.6
  • #38 _gdk_x11_copy_to_image
    from /usr/lib/libgdk-x11-2.0.so.0
  • #39 gdk_drawable_copy_to_image
    from /usr/lib/libgdk-x11-2.0.so.0
  • #40 gdk_pixmap_copy_to_image
    from /usr/lib/libgdk-x11-2.0.so.0
  • #41 gdk_drawable_copy_to_image
    from /usr/lib/libgdk-x11-2.0.so.0
  • #42 gdk_pixbuf_get_from_drawable
    from /usr/lib/libgdk-x11-2.0.so.0
  • #43 panel_background_monitor_get_region
  • #44 panel_background_effective_type
  • #45 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #46 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #47 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #48 ??
  • #49 ??
  • #50 ??
  • #51 ??
  • #52 ??
  • #53 ??
  • #54 __JCR_LIST__
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 __JCR_LIST__
    from /usr/lib/libgtk-x11-2.0.so.0
  • #56 ??
  • #57 ??
  • #58 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0

Comment 4 Vincent Untz 2004-11-25 20:06:13 UTC

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