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 789802 - gnome-shell constantly crashes after closing windows
gnome-shell constantly crashes after closing windows
Status: RESOLVED DUPLICATE of bug 788666
Product: gnome-shell
Classification: Core
Component: general
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-11-02 05:38 UTC by Igor Gnatenko
Modified: 2017-11-02 10:34 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
backtrace (74.92 KB, text/plain)
2017-11-02 05:38 UTC, Igor Gnatenko 		Details

Description Igor Gnatenko 2017-11-02 05:38:10 UTC 
Created attachment 362792 [details]
backtrace

Steps to reproduce:
1. Open Evolution
2. Close Evolution

Actual results:
gnome-shell is restarted after crash

Expected results:
Nothing crashes

gnome-shell-3.26.1-1.fc28.x86_64
libX11-1.6.5-5.fc28.x86_64
mutter-3.26.1-2.fc28.x86_64
mozjs52-52.4.0-1.fc28.x86_64
gjs-1.50.1-1.fc28.x86_64
Comment 1 Igor Gnatenko 2017-11-02 05:42:27 UTC 
Nov 02 06:25:38 ignatenko-w541.localdomain gnome-shell[2119]:
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 32068 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.)



This might be related...
Comment 2 Florian Müllner 2017-11-02 10:34:13 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

(In Fedora's case, it's fixed in mutter-3.26.1-3.fc27 and mutter-3.27.1-1.fc28)

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