gnome-shell crashed with SIGTRAP in g_log_writer_default() from g_log_structured_array() from g_log_structured_array() from g_log_structured_standard("The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadWindow (invalid Window parameter)'.\n (Details: serial 333851 error_code 3 r");

Bug #1821427 reported by Joe Barnett on 2019-03-23
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Medium
Unassigned
mutter (Ubuntu)
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

Had this happen a few times now, where closing the main evolution window (last visible window on desktop) results in a gnome-shell crash (see bug 1821262)

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 22 18:49:10 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2018-09-26 (177 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5
UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
separator:

Joe Barnett (thejoe) wrote :

StacktraceTop:
 XPending (dpy=0x55f60f94d000) at ../../src/Pending.c:55
 gdk_check_xpending (display=0x55f60f95d010) at ../../../../../gdk/x11/gdkeventsource.c:269
 gdk_event_source_prepare (source=<optimized out>, timeout=timeout@entry=0x7ffc22a6a374) at ../../../../../gdk/x11/gdkeventsource.c:287
 g_main_context_prepare (context=context@entry=0x55f60f192e80, priority=priority@entry=0x7ffc22a6a400) at ../../../glib/gmain.c:3499
 g_main_context_iterate (context=0x55f60f192e80, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:3907

Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

I can't find any other reports of a crash like this.

On the slight chance these are related, please uninstall the extensions:

['audio-input-switcher@anduchs', 'audio-output-switcher@anduchs', '<email address hidden>', '<email address hidden>', 'audio-switcher@AndresCidoncha', 'output-audio-devices@muflone']

and then tell us if the problem persists.

summary: - gnome-shell crashed with signal 5 when closing evolution
+ gnome-shell crashed with signal 5 when closing evolution, logging "The
+ program 'gnome-shell' received an X Window System error.\nThis probably
+ reflects a bug in the program.\nThe error was 'BadWindow (invalid Window
+ parameter)'.\n (Details: serial 333851 error_code 3 r"
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Joe Barnett (thejoe) wrote :

problem persisting with extensions uninstalled & disabled:

$ gsettings get org.gnome.shell enabled-extensions
@as []

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Joe Barnett (thejoe) wrote :

Anything else I can do to help debug this?

information type: Private → Public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Daniel van Vugt (vanvugt) wrote :

Unless you can think of anything that's special or unusual about your system that triggers this bug?

It took a while, but we now are getting other reports of this same crash via:
https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

description: updated
Joe Barnett (thejoe) wrote :

Not sure if related, but I do run under wayland (weird that it looks like an X11 error then, especially as evolution runs wayland native?), with fractional zooming on my laptop panel @ 175% and usually have an external, lower resolution screen at 100% scaling. Evolution is usually the first app i open and stays open throughout my session, so has usually been running for days before being closed (and killing the session) -- but sometimes closing it is fine. Haven't seen any other app trigger it.

Daniel van Vugt (vanvugt) wrote :

When you see X11 code in the gnome-shell process of a Wayland session that's nothing unusual. It just means some X11 app is running, talking to Xwayland and gnome-shell (which is both the Wayland display server AND the X11 window manager in this case).

Since this bug is about a particular "BadWindow (invalid Window parameter)", maybe it is specific to Evolution?...

Changed in mutter (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
summary: - gnome-shell crashed with signal 5 when closing evolution, logging "The
- program 'gnome-shell' received an X Window System error.\nThis probably
- reflects a bug in the program.\nThe error was 'BadWindow (invalid Window
- parameter)'.\n (Details: serial 333851 error_code 3 r"
+ gnome-shell crashed with signal 5 in g_log_writer_default() from
+ g_log_structured_array() from g_log_structured_array() from
+ g_log_structured_standard("The program 'gnome-shell' received an X
+ Window System error.\nThis probably reflects a bug in the program.\nThe
+ error was 'BadWindow (invalid Window parameter)'.\n (Details: serial
+ 333851 error_code 3 r");
summary: - gnome-shell crashed with signal 5 in g_log_writer_default() from
+ gnome-shell crashed with SIGTRAP in g_log_writer_default() from
g_log_structured_array() from g_log_structured_array() from
g_log_structured_standard("The program 'gnome-shell' received an X
Window System error.\nThis probably reflects a bug in the program.\nThe
error was 'BadWindow (invalid Window parameter)'.\n (Details: serial
333851 error_code 3 r");
tags: added: eoan
Jean-Louis Dupond (dupondje) wrote :

I have an 100% reliable way to reproduce this crash :)

Take a screenshot & copy to clipboard, try to paste the image (clipboard content) inside a telegram-desktop chat -> BOOM, gnome-shell crashes

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers