Gnome wayland session is getting killed after updating Slowroll to latest version 20240802 released on Aug 10. Rolling back to 20240702 seems to be okay.
No coredump or useful information in either system journal or the wayland user service’s journal. No memory exhaustion or other kernel issues either.
journalctl logs:
Aug 11 23:52:49 suse-pc pipewire[7352]: pw.node: (alsa_output.usb-Topping_DX3_Pro_-00.HiFi__Headphones__sink-54) graph xrun (0 suppressed)
Aug 11 23:52:56 suse-pc nautilus[16304]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc WebExtensions[12343]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc transmission-gtk.desktop[16594]: Gdk-Message: 18:22:56.841: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc gnome-shell[11720]: (EE) failed to read Wayland events: Broken pipe
Aug 11 23:52:56 suse-pc tilix[11345]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc thunderbird-bin[12207]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc xdg-desktop-por[11216]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc gsd-media-keys[7041]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc gsd-color[7026]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc gsd-keyboard[7037]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc gsd-power[7046]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc gsd-wacom[7119]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc xdg-desktop-por[11254]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc systemd[6182]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE
Aug 11 23:52:56 suse-pc evolution-alarm[7079]: Error reading events from display: Broken pipe
Aug 11 23:52:56 suse-pc systemd[6182]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE
Aug 11 23:52:56 suse-pc systemd[6182]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL
org.gnome.Shell@wayland.service logs:
Aug 11 23:46:39 suse-pc gnome-shell[6474]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mozilla.firefox.SearchProvider was not provided by any .service files
Aug 11 23:52:56 suse-pc gnome-shell[11720]: (EE) failed to read Wayland events: Broken pipe
Aug 11 23:52:56 suse-pc systemd[6182]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL
Aug 11 23:52:57 suse-pc systemd[6182]: org.gnome.Shell@wayland.service: Failed with result 'signal'.
Aug 11 23:52:57 suse-pc systemd[6182]: org.gnome.Shell@wayland.service: Triggering OnFailure= dependencies.
Aug 11 23:52:57 suse-pc systemd[6182]: org.gnome.Shell@wayland.service: Consumed 23min 59.621s CPU time.
Thank you so much
Adding MUTTER_DEBUG_KMS_THREAD_TYPE=user to ~/.config/environment.d/00-fixes.conf and rebooting seems to have solved it. At least I can’t reproduce any crashes.
One thing you could try is the MUTTER_DEBUG_KMS_THREAD_TYPE=user environment variable. There have been a couple of reports of gnome-shell getting killed if the driver is stalling the RT KMS thread too long and this prevents RT from being used.
Guess the problem surfaced now due to some amdgpu changes in the new 6.10.3 kernel
This did solve the issue, but there is some minor artifacting in Gnome apps (Console, calculator) when I have Youtube playing but can definitely live with it!
Apparently the extension is worse for performance so the workaround adding MUTTER_DEBUG_KMS_THREAD_TYPE=user to ~/.config/environment.d/00-fixes.conf is still the recommended method to deal with this problem.
Root cause of the issue is a bug/regression in amdgpu kernel driver.
i find the mutter thread fix causes random reboots when idle… maybe garbage collection killing the “user thread” or something. i installed kernel 6.9.9. all stable on that.