-
-
Notifications
You must be signed in to change notification settings - Fork 480
Closed
Description
This is the error:
The program 'python' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1064 error_code 3 request_code 3 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.)
Reproducible in hello_world.py, tkinter_.py and some other examples. It happens when setting parent=NULL
in print_handler_gtk.cpp, but also occurs when setting parent=CefBrowser_GetGtkWindow(browser_)
.
When clicking "Print" button in the dialog then everything works fine, there is no error. The error occurs only when clicking "X" close button in the print dialog.
In cefclient when closing print dialog there is also X window error:
[0611/191953.156656:WARNING:x11_util.cc(1362)] X error received: serial 9030, error_code 181 (GLXBadWindow), request_code 154, minor_code 32 (Unknown)
[0611/191953.158543:WARNING:x11_util.cc(1362)] X error received: serial 9032, error_code 9 (BadDrawable), request_code 153, minor_code 4 (Unknown)
[0611/191953.158695:WARNING:x11_util.cc(1362)] X error received: serial 9033, error_code 3 (BadWindow), request_code 4, minor_code 0 (Unknown)
However in cefclient it doesn't result in app termination. It seems that to resolve the issue it is required to install x11 error handlers that will ignore the badwindow error.