GNOME Bugzilla – Bug 600891
BadDrawable (invalid Pixmap or Window parameter error when using GtkPlug
Last modified: 2015-01-11 20:31:02 UTC
Hi All I am using GtkPlug/GtkSocket in my application but whenever there is key press event ..i get a gdk_x_error with following parameters The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 26960 error_code 9 request_code 53 minor_code 0) This piece of code used to work perfectly on gtk2.16 ,but crashes on gtk 2.18 and I am using gtk_socket_get_id to get Native window id of socket window and passing this to the GtkPlug to create a plug using gtk_plug_construct .Could it be because of client side window functionality?
I think this might be the same bug I and other Rox users have been experiencing. It uses GtkPlug/Socket to implement panel applets, and it keeps crashing with "X Window System errors" when adding a new applet. I found that in an applet I was developing I could greatly reduce the frequency of the crashes by calling gtk_widget_show on the plug before adding child widgets, but I'm not sure it entirely cured the problem. IIRC I did see the BadDrawable error sometimes, but the one I trapped a few weeks ago had a different error: ** (rox:12764): WARNING **: The program 'rox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 27704 error_code 2 request_code 53 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.) ... Program terminated with signal 6, Aborted.
+ Trace 219475
I couldn't get it to crash today by adding applets, but I found that by quitting a certain applet I got a crash every time, but only if I ran Rox with --sync. FYI the following backtrace is for gtk 2.18.4-1 from debian sid, I think the previous one was from 2.18.1. ** (rox:3409): WARNING **: The program 'rox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 18588 error_code 9 request_code 53 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.) ** (rox:3409): WARNING **: We got a BadWindow error from the X server. This might be due to this GTK bug (during drag-and-drop?): http://bugzilla.gnome.org/show_bug.cgi?id=152151 Trying to continue... ** (rox:3409): WARNING **: The program 'rox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadPixmap (invalid Pixmap parameter)'. (Details: serial 18589 error_code 4 request_code 54 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.) /home/tony/Rox/PanelClock/clock.py:18: GtkDeprecationWarning: gtk.timeout_remove is deprecated, use gobject.source_remove instead g.timeout_remove(timeout) Aborted
+ Trace 219476
This may have been fixed by commit 430ea2fff639f31b868e025002a32ba473c7bd07