You are not logged in.

#1 2021-04-27 05:13:40

jrop
Member
Registered: 2021-04-08
Posts: 10

gnome-shell intermittently crashes upon resume

Every once in a while, after upgrading to GNOME 40, when I attempt to wake my system from suspend by opening the lid of my laptop, I am greeted by a blank TTY (black screen) with no prompt, and a few "^@^@" symbols.  After switching to a new TTY and capturing the JournalD logs, this is what I get:

https://pastebin.com/XDgJ8YVE

Sometimes, after a while, gnome-shell is relaunched, and I have to log in and start all of my programs again.

Now, the lines of interest (at least to me):

...
Apr 26 22:45:58 my-laptop gnome-shell[2288]: (EE) failed to write to XWayland fd: Broken pipe
...
Apr 26 22:46:00 my-laptop systemd-coredump[132347]: Process 2088 (gnome-shell) of user 1000 dumped core.
                                                          Stack trace of thread 2088:
                                                          #0  0x00007f4bf22b8ef5 n/a (n/a + 0x0)
...

It seems like XWayland is dying during resuming my laptop.  Does anybody have any tips for me to debug this?  I have already cleared all of my GNOME data and started fresh, so I'm not sure exactly what could be causing this.

Offline

#2 2021-04-27 06:00:26

seth
Member
Registered: 2012-09-03
Posts: 21,303

Re: gnome-shell intermittently crashes upon resume

Apr 26 22:45:58 my-laptop gnome-documents[2588]: Error reading events from display: Broken pipe
Apr 26 22:45:58 my-laptop gnome-calendar[2596]: Error reading events from display: Broken pipe
Apr 26 22:45:58 my-laptop xdg-desktop-por[4901]: Error reading events from display: Broken pipe
Apr 26 22:45:58 my-laptop gsd-media-keys[2315]: Error reading events from display: Broken pipe
Apr 26 22:45:58 my-laptop gsd-wacom[2347]: Error reading events from display: Broken pipe
Apr 26 22:45:58 my-laptop gsd-keyboard[2313]: Error reading events from display: Broken pipe
Apr 26 22:45:58 my-laptop gsd-color[2304]: Error reading events from display: Broken pipe
Apr 26 22:45:58 my-laptop evolution-alarm[2330]: Error reading events from display: Broken pipe
Apr 26 22:45:58 my-laptop gsd-power[2316]: Error reading events from display: Broken pipe

It's not only xwayland - the wayland server is gone.
I assume this happened before the S3, but that part is not in the journal excerpt.

Offline

#3 2021-04-27 21:50:34

jrop
Member
Registered: 2021-04-08
Posts: 10

Re: gnome-shell intermittently crashes upon resume

Here is the full log (I had to truncate the one above to fit on PasteBin).  At any rate, sprunge.us does not seem to have the same limitation.

http://sprunge.us/cS8GYM

Offline

#4 2021-04-28 05:46:14

seth
Member
Registered: 2012-09-03
Posts: 21,303

Re: gnome-shell intermittently crashes upon resume

Apr 26 21:47:40 my-laptop systemd-logind[580]: Lid closed.
Apr 26 21:47:40 my-laptop systemd-logind[580]: Suspending...
Apr 26 21:47:40 my-laptop NetworkManager[579]: <info>  [1619495260.4905] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 26 21:47:40 my-laptop NetworkManager[579]: <info>  [1619495260.4907] device (enp2s0f0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 26 21:47:40 my-laptop gnome-shell[2088]: JS ERROR: Error getting systemd inhibitor: Gio.IOErrorEnum: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running
                                                   _promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:418:45
                                                   ### Promise created here: ###
                                                   inhibit@resource:///org/gnome/shell/misc/loginManager.js:196:35
                                                   _syncInhibitor@resource:///org/gnome/shell/ui/screenShield.js:211:32
Apr 26 21:47:40 my-laptop NetworkManager[579]: <info>  [1619495260.8006] device (58:CB:52:2A:72:B6): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 26 21:47:40 my-laptop NetworkManager[579]: <info>  [1619495260.8017] device (p2p-dev-wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 26 21:47:40 my-laptop NetworkManager[579]: <info>  [1619495260.8024] manager: NetworkManager state is now ASLEEP
Apr 26 21:47:40 my-laptop NetworkManager[579]: <info>  [1619495260.8031] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Apr 26 21:47:40 my-laptop dbus-daemon[578]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=579 comm="/usr/bin/NetworkManager
 --no-daemon ")
Apr 26 21:47:40 my-laptop systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 26 21:47:40 my-laptop dbus-daemon[578]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 26 21:47:40 my-laptop systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 26 21:47:40 my-laptop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 21:47:40 my-laptop kernel: audit: type=1130 audit(1619495260.953:346): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=
success'
Apr 26 21:47:40 my-laptop kernel: wlp3s0: deauthenticating from 10:0c:6b:5e:93:c2 by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 26 21:47:40 my-laptop wpa_supplicant[1001]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=10:0c:6b:5e:93:c2 reason=3 locally_generated=1
Apr 26 21:47:40 my-laptop wpa_supplicant[1001]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
Apr 26 21:47:40 my-laptop NetworkManager[579]: <info>  [1619495260.9965] device (wlp3s0): supplicant interface state: completed -> disconnected
Apr 26 21:47:40 my-laptop NetworkManager[579]: <info>  [1619495260.9968] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Apr 26 21:47:40 my-laptop gnome-shell[2088]: An active wireless connection, in infrastructure mode, involves no access point?
Apr 26 21:47:41 my-laptop NetworkManager[579]: <info>  [1619495261.0687] dhcp4 (wlp3s0): canceled DHCP transaction
Apr 26 21:47:41 my-laptop NetworkManager[579]: <info>  [1619495261.0688] dhcp4 (wlp3s0): state changed bound -> terminated
Apr 26 21:47:41 my-laptop NetworkManager[579]: <info>  [1619495261.0732] device (wlp3s0): set-hw-addr: set MAC address to F6:A7:D4:CF:18:82 (scanning)
Apr 26 21:47:41 my-laptop NetworkManager[579]: <info>  [1619495261.1153] device (wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Apr 26 21:47:41 my-laptop NetworkManager[579]: <info>  [1619495261.1194] device (wlp3s0): set-hw-addr: reset MAC address to A8:7E:EA:BA:3A:C4 (unmanage)
Apr 26 21:47:41 my-laptop systemd[1]: Reached target Sleep.
Apr 26 21:47:41 my-laptop systemd[1]: Starting Suspend...
Apr 26 21:47:41 my-laptop wpa_supplicant[1001]: nl80211: deinit ifname=p2p-dev-wlp3s0 disabled_11b_rates=0
Apr 26 21:47:41 my-laptop gnome-shell[2088]: **
Apr 26 21:47:41 my-laptop gnome-shell[2088]: mutter:ERROR:../mutter/src/backends/native/meta-kms-update.c:340:meta_kms_update_set_power_save: assertion failed: (!update->crtc_gammas)
Apr 26 21:47:41 my-laptop gnome-shell[2088]: Bail out! mutter:ERROR:../mutter/src/backends/native/meta-kms-update.c:340:meta_kms_update_set_power_save: assertion failed: (!update->crtc_gammas)
Apr 26 21:47:41 my-laptop kernel: audit: type=1701 audit(1619495261.673:347): auid=1000 uid=1000 gid=1000 ses=4 pid=2088 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=6 res=1
Apr 26 21:47:41 my-laptop audit[2088]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=4 pid=2088 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=6 res=1
Apr 26 21:47:41 my-laptop gnome-shell[2088]: == Stack trace for context 0x55bcacf9c1e0 ==
Apr 26 21:47:41 my-laptop kernel: usb usb2: root hub lost power or was reset
Apr 26 21:47:41 my-laptop kernel: usb usb3: root hub lost power or was reset
Apr 26 21:47:41 my-laptop kernel: xhci_hcd 0000:05:00.0: Zeroing 64bit base registers, expecting fault
Apr 26 21:47:41 my-laptop systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Apr 26 21:47:41 my-laptop audit: BPF prog-id=53 op=LOAD
Apr 26 21:47:41 my-laptop audit: BPF prog-id=54 op=LOAD
Apr 26 21:47:41 my-laptop audit: BPF prog-id=55 op=LOAD
Apr 26 21:47:41 my-laptop systemd[1]: Started Process Core Dump (PID 132346/UID 0).
Apr 26 21:47:41 my-laptop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-132346-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 26 21:47:41 my-laptop kernel: audit: type=1334 audit(1619495261.813:348): prog-id=53 op=LOAD
Apr 26 21:47:41 my-laptop kernel: audit: type=1334 audit(1619495261.813:349): prog-id=54 op=LOAD
Apr 26 21:47:41 my-laptop kernel: audit: type=1334 audit(1619495261.813:350): prog-id=55 op=LOAD
Apr 26 21:47:41 my-laptop kernel: audit: type=1130 audit(1619495261.813:351): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-132346-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re
s=success'
Apr 26 21:47:41 my-laptop wpa_supplicant[1001]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Apr 26 21:47:42 my-laptop systemd-sleep[132172]: Suspending system...
Apr 26 21:47:42 my-laptop kernel: PM: suspend entry (deep)

Happens twice, the second time the core is preserved (but is just an abort)

Apr 27 15:44:18 my-laptop systemd-coredump[571681]: Process 134328 (gnome-shell) of user 1000 dumped core.
                                                          
                                                          Stack trace of thread 134328:
                                                          #0  0x00007fb6c0904ef5 raise (libc.so.6 + 0x3cef5)
                                                          #1  0x00005618862f0a39 n/a (gnome-shell + 0x2a39)
                                                          #2  0x00007fb6c0904f80 __restore_rt (libc.so.6 + 0x3cf80)
                                                          #3  0x00007fb6c0904ef5 raise (libc.so.6 + 0x3cef5)
                                                          #4  0x00007fb6c08ee862 abort (libc.so.6 + 0x26862)
                                                          #5  0x00007fb6c1752084 n/a (libglib-2.0.so.0 + 0x1d084)
                                                          #6  0x00007fb6c17ad85d g_assertion_message_expr (libglib-2.0.so.0 + 0x7885d)
                                                          #7  0x00007fb6c0c060ae n/a (libmutter-8.so.0 + 0x16f0ae)
                                                          #8  0x00007fb6c0b00e05 n/a (libmutter-8.so.0 + 0x69e05)
                                                          #9  0x00007fb6c187cddf g_closure_invoke (libgobject-2.0.so.0 + 0x12ddf)
                                                          #10 0x00007fb6c18a5fbd n/a (libgobject-2.0.so.0 + 0x3bfbd)
                                                          #11 0x00007fb6c1899cad g_signal_emit_valist (libgobject-2.0.so.0 + 0x2fcad)
                                                          #12 0x00007fb6c189a210 g_signal_emit (libgobject-2.0.so.0 + 0x30210)
                                                          #13 0x00007fb6c18843e6 n/a (libgobject-2.0.so.0 + 0x1a3e6)
                                                          #14 0x00007fb6c187d3f0 n/a (libgobject-2.0.so.0 + 0x133f0)
                                                          #15 0x00007fb6c188cf76 g_object_setv (libgobject-2.0.so.0 + 0x22f76)
                                                          #16 0x00007fb6c188d08c g_object_set_property (libgobject-2.0.so.0 + 0x2308c)
                                                          #17 0x00007fb6c0adf8f9 n/a (libmutter-8.so.0 + 0x488f9)
                                                          #18 0x00007fb6c19baab1 n/a (libgio-2.0.so.0 + 0xf6ab1)
                                                          #19 0x00007fb6c1788f30 g_main_context_dispatch (libglib-2.0.so.0 + 0x53f30)
                                                          #20 0x00007fb6c17dcb59 n/a (libglib-2.0.so.0 + 0xa7b59)
                                                          #21 0x00007fb6c1788593 g_main_loop_run (libglib-2.0.so.0 + 0x53593)
                                                          #22 0x00007fb6c0b683e3 meta_run (libmutter-8.so.0 + 0xd13e3)
                                                          #23 0x00005618862f042a n/a (gnome-shell + 0x242a)
                                                          #24 0x00007fb6c08efb25 __libc_start_main (libc.so.6 + 0x27b25)
                                                          #25 0x00005618862f065e n/a (gnome-shell + 0x265e)
                                                          
                                                          Stack trace of thread 134363:
                                                          #0  0x00007fb6bff119ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
                                                          #1  0x00007fb6bff0b260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
                                                          #2  0x00007fb6aa8ed9ec n/a (/usr/lib/dri/radeonsi_dri.so (deleted) + 0x1529ec)

I can't find an upstream bug, you'll have to file one.
meta_kms_update_set_power_save seems to expect meta_kms_update_free to have taken place an either that didn't happen or there's a concurrent meta_kms_crtc_gamma_new call.

Offline

#5 2021-04-28 22:20:13

jrop
Member
Registered: 2021-04-08
Posts: 10

Re: gnome-shell intermittently crashes upon resume

http://sprunge.us/2U2I9X

Got a little different error after the recent update of gnome-shell.

Offline

#6 2021-04-28 22:32:41

jrop
Member
Registered: 2021-04-08
Posts: 10

Re: gnome-shell intermittently crashes upon resume

I created this upstream issue: https://gitlab.gnome.org/GNOME/gnome-sh … ssues/4201

Hopefully the GNOME team can shed light on the issue.

Offline

#7 2021-04-29 09:24:08

j-james
Member
From: Johto
Registered: 2021-04-29
Posts: 6
Website

Re: gnome-shell intermittently crashes upon resume

I've also been encountering this. Sometimes, it does the black screen with @ symbols and boots into the logged out state after a couple of seconds, but sometimes the computer goes black (with no backlight) and is unresponsive until a power cycle.

Offline

#8 2021-04-30 04:14:42

jrop
Member
Registered: 2021-04-08
Posts: 10

Re: gnome-shell intermittently crashes upon resume

@j-james Up until GNOME 40 got released, my Arch install was rock solid.  It feels lame to have it this unstable, but I guess that comes with the territory.  It's good to know I'm not the only one experiencing this issue.

Offline

#9 2021-04-30 05:51:01

seth
Member
Registered: 2012-09-03
Posts: 21,303

Re: gnome-shell intermittently crashes upon resume

sometimes the computer goes black (with no backlight) and is unresponsive until a power cycle

That's not a userspace crash, though.
I assume you mean this to happen when waking up from S3?
nvidia?

Offline

#10 2021-05-01 03:39:17

j-james
Member
From: Johto
Registered: 2021-04-29
Posts: 6
Website

Re: gnome-shell intermittently crashes upon resume

Funny, GNOME 38 overall was significantly less stable for me (a particularly nasty bug involved not being able to exit the wifi menu - and because it takes over the whole screen and inhibits controls, needing to reboot and lose anything not saved).

Suspend-to-ram, yes, but on Intel i7 and UHD Integrated Graphics. I think it's likely some resulting bug from the bug you're dealing with. Far less frequent than the black screen with @ symbols.

Offline

#11 2021-05-01 06:23:06

seth
Member
Registered: 2012-09-03
Posts: 21,303

Re: gnome-shell intermittently crashes upon resume

i915.enable_dc=0 i915.enable_fbc=0 i915.enable_psr=0

What kind of output? HDMI?

"^@" is "null" - some input device likely creates that and the console just prints it. It's not necessarily related.

Offline

#12 2021-05-02 04:22:38

jrop
Member
Registered: 2021-04-08
Posts: 10

Re: gnome-shell intermittently crashes upon resume

In my case I am running AMD.  It only seems to occur after the laptop has been asleep for a long period of time (i.e., overnight).  gnome-shell just updated again when I ran updates, so we will see if the problem persists.

Offline

#13 2021-05-02 06:36:26

seth
Member
Registered: 2012-09-03
Posts: 21,303

Re: gnome-shell intermittently crashes upon resume

The original crash is a HW agnostic bug in gnome-shell, #7 introduced an unrelated (though possibly subsequent) bug.

Offline

#14 2021-05-03 00:55:18

jrop
Member
Registered: 2021-04-08
Posts: 10

Re: gnome-shell intermittently crashes upon resume

Ever since installing gnome-shell@1:40.0+67+g79acae417-1, things seem to be _much_ more stable.  I haven't had a crash yet, but I will keep monitoring the situation.

Offline

Board footer

Powered by FluxBB