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 788729 - gnome-shell crashes with 'BadWindow (invalid Window parameter)'
gnome-shell crashes with 'BadWindow (invalid Window parameter)'
Status: RESOLVED DUPLICATE of bug 788666
Product: gnome-shell
Classification: Core
Component: window-management
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-10-09 17:56 UTC by Henry Snow
Modified: 2017-10-09 21:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Henry Snow 2017-10-09 17:56:18 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

Thread 1 (Thread 0x7ffff7f79a00 (LWP 2583))

  • #0 0x00007ffff6b0ecd2 in
  • #1 g_log_writer_default
  • #2 g_log_structured_array
  • #3 g_log_structured
  • #4 0x00007ffff486a454 in
  • #5 0x00007ffff4877e05 in
  • #6 _XError
  • #7 0x00007ffff3d1c617 in
  • #8 0x00007ffff3d1c6d5 in
  • #9 _XReply
  • #10 XSync
  • #11 0x00007ffff486944f in
  • #12 0x00007ffff483a76f in
  • #13 0x00007ffff4fde5ed in
  • #14 0x00007ffff4fe1b17 in
  • #15 meta_window_actor_effect_completed
  • #16 ffi_call_unix64
  • #17 ffi_call
  • #18 0x00007ffff5a9acbb in
  • #19 0x00007ffff5a9c617 in
  • #20 0x00001a87873a9810 in
  • #21 0x00007fffb1418a00 in
  • #22 0x00007fffffffc9f0 in
  • #23 0x0000000000000000 in
== 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
Comment 1 Florian Müllner 2017-10-09 18:30:25 UTC
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 ...
Comment 2 Henry Snow 2017-10-09 21:15:29 UTC
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 ***