[Dell XPS 15 9575] gnome-shell crashes with segfault on suspend-by-lid-close in Wayland session

[Mario Vukelic]

In an X session, suspend and wakeup works when initiated either by lid close or from panel menu.

In a Wayland session, suspend and wakeup works only when initiated from panel menu.
However, gnome-shell segfaults when suspend is initiated by lid close.
When reopening the lid, I am back at the login screen for a new session.

(When suspend-on-lid-close is disabled in Gnome Tweaks, gnome-shell and the Wayland session survive the lid close)

In dmesg I find the gnome-shell segfault every time, here on the second line:

[ 139.420519] wlp2s0: deauthenticating from e0:28:6d:5d:ab:1b by local choice (Reason: 3=DEAUTH_LEAVING)
[ 139.964629] gnome-shell[4166]: segfault at fffffffffffffbc8 ip 00007fd049223eb8 sp 00007ffdda00d6e0 error 5 in libst-1.0.so[7fd0491fd000+2b000]
[ 139.964633] Code: 00 00 48 8d 3d 67 78 00 00 e9 44 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d eb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d
[ 140.063376] rfkill: input handler enabled
[ 140.603550] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
[ 140.723020] [drm] UVD and UVD ENC initialized successfully.
[ 140.832956] [drm] VCE initialized successfully.
[ 140.951177] PM: suspend entry (deep)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 25 21:13:44 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (72 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Daniel van Vugt (vanvugt)]

Also, you may wish to try disabling your gnome-shell extensions, since extensions tend to cause many of the bugs that we see...

b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'suspend-button@laserb', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'removeaccesibility@lomegor', '<email address hidden>', '<email address hidden>']"

[Mario Vukelic (kreuzsakra)]

Oopsie, indeed the crash on lid close is gone after disabling extensions. Even the very act of turning off the overall extension switch in Tweaks crashes the session.
Will figure out the culprit extension then.