Hey,
Yesterday I upgraded from Fedora 40 to 41. Everything seemed to run fine (all programs I tried worked), until I tried to run the game Brotato today. When the game window opens my screen becomes black and after a few seconds I get the login screen. Looks like the rendering of the game crashes my user session. (Screen is not just locked, my session is gone, all programs closed)
I don’t know how to get proper logs, because if I run it from the terminal the terminal gets closed when my session crashes as well. How can I do that and how could I fix that problem?
I have the same issue with the Factorio game. Crash appears randomly, while playing or more frequently while switching between Firefox and Factorio (fullscreen).
Here is my log when the gdm has crashed.
It happened at 13:41:23. Wayland was just killed and that’s all.
journalctl --no-host --no-pager --since -5m
Nov 13 13:41:14 wpa_supplicant[1370]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-44 noise=9999 txrate=1921500
Nov 13 13:41:17 wpa_supplicant[1370]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-44 noise=9999 txrate=1921500
Nov 13 13:41:20 wpa_supplicant[1370]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-44 noise=9999 txrate=1921500
Nov 13 13:41:23 gnome-shell[5037]: (EE) failed to read Wayland events: Broken pipe
Nov 13 13:41:23 unknown[3299]: Lost connection to Wayland compositor.
Nov 13 13:41:23 unknown[19439]: Lost connection to Wayland compositor.
Nov 13 13:41:23 unknown[2638]: Error reading events from display: Broken pipe
Nov 13 13:41:23 unknown[3381]: Error reading events from display: Broken pipe
Nov 13 13:41:23 unknown[2642]: Error reading events from display: Broken pipe
Nov 13 13:41:23 unknown[2612]: Error reading events from display: Broken pipe
Nov 13 13:41:23 unknown[2707]: Error reading events from display: Broken pipe
Nov 13 13:41:23 unknown[2749]: Error reading events from display: Broken pipe
Nov 13 13:41:23 unknown[2627]: Error reading events from display: Broken pipe
Nov 13 13:41:23 systemd[2312]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL
Nov 13 13:41:23 systemd[2312]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 13:41:23 unknown[2680]: Lost connection to Wayland compositor.
Nov 13 13:41:23 systemd[2312]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 13:41:23 systemd[2312]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 13:41:23 systemd[2312]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 13:41:23 systemd[2312]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 13:41:23 systemd[2312]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 13:41:23 systemd[2312]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'.
Nov 13 13:41:23 systemd[2312]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 13:41:23 systemd[2312]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Nov 13 13:41:23 systemd[2312]: dbus-:1.2-org.gnome.Ptyxis@0.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 13:41:23 systemd[2312]: dbus-:1.2-org.gnome.Ptyxis@0.service: Failed with result 'exit-code'.
Nov 13 13:41:23 systemd[2312]: dbus-:1.2-org.gnome.Ptyxis@0.service: Consumed 1.604s CPU time, 241.6M memory peak, 19.6M memory swap peak.
Nov 13 13:41:23 unknown[3301]: Error reading events from display: Broken pipe
Nov 13 13:41:23 telegram-deskto[5309]: Error reading events from display: Broken pipe
Nov 13 13:41:23 systemd[2312]: app-gnome-org.gnome.Software-2680.scope: Consumed 32.812s CPU time, 868.3M memory peak, 519.8M memory swap peak.
Nov 13 13:41:23 systemd[2312]: app-flatpak-org.qbittorrent.qBittorrent-2701.scope: Consumed 6min 45.505s CPU time, 9.2G memory peak, 42.1M memory swap peak.
Which GPU do you use? I think I can trigger the same bug (unreliably) when opening a game or HW accelerated video (e.g. with mpv). Sometimes the video or game is already running, and switching windows crashes the session.
Sadly, I haven’t found anything useful in the logs. dmesg does not contain an amdgpu error. And in journald logs, I only see “broken pipes” and “Lost connection to Wayland compositor” messages.
When checking gdm it does not appear to have crashed which can be observed with systemctl status gdm
and by this log message:
Dez 08 19:44:54 gdm[3625]: Gdm: Child process -599079 was already dead.
My graphics is RX Vega 7 (which is onboard), my CPU is the 5500U and my device a laptop. I switched from Vulkan to the old rendering and that fixed the problem for me, in some time I’ll try to go back to the new Vulkan and see if the problem persists, but currently I don’t have the time and resources
I haven’t changed anything and the issue did not appear for a long time.
So i guess an update fixed it.