I was able to get this freeze to happen again. Since my local session
was hung, I logged in to the affected machine via SSH.
Here's the relevant entries from /var/log/syslog:
2026-06-29T18:17:29.898965-07:00 [hostname-redacted] kernel: amdgpu
0000:07:00.0: VM memory stats for proc Xwayland(27826) task Xwayland:cs0(27825)
is non-zero when fini
2026-06-29T18:17:29.899616-07:00 [hostname-redacted] gnome-shell[14222]: X
Wayland crashed; attempting to recover
2026-06-29T18:17:29.900978-07:00 [hostname-redacted] kernel: amdgpu
0000:07:00.0: VM memory stats for proc (0) task (0) is non-zero when fini
2026-06-29T18:17:29.901510-07:00 [hostname-redacted] systemd[5954]: Stopped
target gnome-session-x11-services-ready.target - GNOME session X11 services.
2026-06-29T18:17:29.901628-07:00 [hostname-redacted] systemd[5954]:
Stopping org.gnome.SettingsDaemon.XSettings.service - GNOME XSettings service...
2026-06-29T18:17:29.902695-07:00 [hostname-redacted] gsd-xsettings[27840]:
XIO: fatal IO error 4 (Interrupted system call) on X server
"unix:/tmp/.X11-unix/X1"
2026-06-29T18:17:29.902730-07:00 [hostname-redacted] gsd-xsettings[27840]:
after 25 requests (25 known processed) with 0 events remaining.
2026-06-29T18:17:29.903994-07:00 [hostname-redacted] systemd[5954]:
org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited,
status=1/FAILURE
2026-06-29T18:17:29.918766-07:00 [hostname-redacted] systemd[5954]:
org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'.
2026-06-29T18:17:29.919121-07:00 [hostname-redacted] systemd[5954]: Stopped
org.gnome.SettingsDaemon.XSettings.service - GNOME XSettings service.
2026-06-29T18:17:29.919202-07:00 [hostname-redacted] systemd[5954]:
org.gnome.SettingsDaemon.XSettings.service: Consumed 3.763s CPU time over 1d 2h
39min 40.006s wall clock time, 13.6M memory peak.
2026-06-29T18:17:29.919385-07:00 [hostname-redacted] systemd[5954]: Stopped
target gnome-session-x11-services.target - GNOME session X11 services.
2026-06-29T18:17:29.922783-07:00 [hostname-redacted] systemd[5954]:
snap.boinctasks-js.boinctasks-js-[id-redacted].scope: Consumed 2min 4.062s CPU
time over 1d 52min 4.934s wall clock time, 399.9M memory peak.
2026-06-29T18:17:29.909961-07:00 [hostname-redacted] kernel: amdgpu
0000:07:00.0: VM memory stats for proc (0) task (0) is non-zero when fini
2026-06-29T18:17:29.935346-07:00 [hostname-redacted] kernel: amdgpu
0000:07:00.0: VM memory stats for proc steamwebhelper(84389) task
steamwebhe:cs0(84227) is non-zero when fini
2026-06-29T18:17:29.941955-07:00 [hostname-redacted] kernel: amdgpu
0000:07:00.0: VM memory stats for proc steam(84020) task steam:cs0(83967) is
non-zero when fini
2026-06-29T18:17:29.952959-07:00 [hostname-redacted] kernel: amdgpu
0000:07:00.0: VM memory stats for proc steamwebhelper(84261) task
steamwebhe:cs0(84257) is non-zero when fini
2026-06-29T18:17:30.400795-07:00 [hostname-redacted] systemd[5954]:
app-gnome-steam-82747.scope: Consumed 28min 11.108s CPU time over 19h 42min
6.390s wall clock time, 11.5G memory peak.
> the next time it happens please force the shell to dump core: sudo
killall -USR1 gnome-shell
I ran this command from within my SSH session, and it cleared the screen
and returned my local console to the GNOME login prompt.
> 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.
There is no crash file that is obviously related to this particular
hang. The most recent file is several days old, and unrelated to gnome-
shell, xwayland, or the game.
> 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.
This brings me to a page that simply says "No errors have been reported
from this system".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2158513
Title:
Exiting a game running in XWayland intermittently causes the GNOME
shell to hang
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2158513/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
