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 148857 - gdk_x_error while using the gdk_pixbuf_get_from_drawable
gdk_x_error while using the gdk_pixbuf_get_from_drawable
Status: RESOLVED DUPLICATE of bug 146075
Product: gnome-panel
Classification: Other
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2004-07-30 10:43 UTC by Vasista Sarma
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Vasista Sarma 2004-07-30 10:43:54 UTC
This crash has occured while trying to change the Desktop background by making
the panel transparent repeated change of desktop background makes the panel
crash as it tries to put its background as its own background to show that it is
 transparent.

I have traced back the code and it is failing and returning this error when i
tried GDB i could find the back trace i am attaching the back trace and the
error pop'ed up.

The function call at which it was failing was gdk_pixbuf_get_from_drawable()

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 3124 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.)
 
Program exited with code 01.



BACK TRACE USING GDB::

Thread 1088658688 (LWP 27583)

  • #0 gdk_x_error
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #1 bonobo_x_error_handler
    from /opt/gnome/lib/libbonoboui-2.so.0
  • #2 _XError
    from /usr/X11R6/lib/libX11.so.6
  • #3 _XReply
    from /usr/X11R6/lib/libX11.so.6
  • #4 XSync
    from /usr/X11R6/lib/libX11.so.6
  • #5 _XSyncFunction
    from /usr/X11R6/lib/libX11.so.6
  • #6 XCopyArea
    from /usr/X11R6/lib/libX11.so.6
  • #7 _gdk_x11_copy_to_image
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 static_fundamental_type_nodes
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #18 __JCR_LIST__
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 g_object_new_valist
    from /opt/gnome/lib/libgobject-2.0.so.0

Comment 1 Owen Taylor 2004-07-30 15:01:06 UTC
Not entirely sure how you get a BadGC here, but almost certainly
a panel bug of some type.

The information you need to provide the panel maintainers is what is
distinct about your system ... remember, if it crashed for everybody
else, the bug would have already been fixed. 

You might want to attach (as an attachmet) the output of 'xdyinfo' - that's 
often useful in debugging this type of thing. Also make sure that
you are running the Panel with --sync as described in the error
message.
Comment 2 Vincent Untz 2004-08-17 12:25:39 UTC

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