GNOME Bugzilla – Bug 788729
gnome-shell crashes with 'BadWindow (invalid Window parameter)'
Last modified: 2017-10-09 21:15:29 UTC
Running arch linux + gnome 3.26. gnome-shell crashes when PyCharm Community Edition 2017.2 reaches the New/Open project screen. This did not occur before upgrade to 3.26. To reproduce w/ PyCharm: 1. Launch PyCharm 2. Close automatically opened project 3. Crash $> gnome-shell --version GNOME Shell 3.26.1 $> uname -r 4.13.4-1-ARCH gnome-shell -> journalctl: gnome-shell[846]: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 35488 error_code 3 request_code 18 (core protocol) 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 GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) gdb stacktrace: Thread 1 "gnome-shell" received signal SIGTRAP, Trace/breakpoint trap. 0x00007ffff6b0ecd2 in ?? () from /usr/lib/libglib-2.0.so.0 (gdb) t a a bt
+ Trace 238037
Thread 1 (Thread 0x7ffff7f79a00 (LWP 2583))
== Stack trace for context 0x5555559db170 == #0 0x7fffffffcad0 b resource:///org/gnome/shell/ui/windowManager.js:1379 (0x7fffb14361a8 @ 578) #1 0x7fffffffcb40 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fffd80c2c48 @ 71) #2 0x7fffffffcbd0 I self-hosted:917 (0x7fffd80ee4d8 @ 394) $1 = 1433843680 (gdb) quit
Possibly a duplicate of bug 788666, but hard to tell from a backtrace with missing debug symbols. Unfortunately Arch doesn't have separate debug symbols that can be installed, so users need to recompile packages themselves to do meaningful backtraces ...
I'd buy that this is a duplicate. Only occurs w/ X, not wayland. PyCharm close project closes a maximized window, as described by the other bug. *** This bug has been marked as a duplicate of bug 788666 ***