Have you checked for system updates?: Yes (no pending packages were listed)
Steam Logs: Relevant redacted excerpts and the uploaded minidump CrashID are below. I have not attached the raw archive because it contains Steam account identifiers and unrelated private data.
Please describe your issue in as much detail as possible
Expected: after the Xfce screensaver locks/blanks the display, unlocking should return to the running game and responsive desktop.
Actual: I left EZ2ON running through Proton Hotfix and the Xfce session entered its idle lock/blank state. Immediately after unlocking, the graphical session appeared completely unresponsive. I waited for at least one minute and then forced a hardware reset. I did not try switching to a VT or connecting over SSH before resetting.
This is the first time I have seen the issue and I have not deliberately retried it because recovery required a hard reset.
The previous-boot journal and Steam logs show that this was not a normal system suspend/resume. Background userspace services continued logging for about 75 seconds after the unlock, until the forced reset, so the kernel and at least part of userspace were still alive while the X11 desktop was unresponsive.
Steam's CEF GPU process exited after the unlock, then Steam asserted that its main loop had been stalled for more than 15 seconds. Steam uploaded the corresponding minidump successfully:
[2026-08-22 04:56:40] GPU process exited unexpectedly: exit_code=512
[2026-08-22 04:56:46] src/clientdll/steamengine.cpp (2843) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled
[2026-08-22 04:56:47] Finished uploading minidump (out-of-process): success = yes
[2026-08-22 04:56:47] CrashID=bp-ad7b7571-1590-4cad-ba8a-70a442260821
Timeline from the previous boot (KST, UTC+09:00):
04:50:15 EZ2ON launched through Proton Hotfix
04:55:01 Last Xorg EDID/RandR activity before the unlock
04:55:37 Steam tracked the game under a new process; overlay started
04:56:23 xfce4-screensaver-dialog PAM account hook (unlock timing anchor)
04:56:36 at-spi2-registryd disabled one unresponsive application
04:56:40 Steam CEF GPU process exited with exit_code=512
04:56:46 Steam BMainLoop >15-second stall assertion
04:56:47 Steam minidump upload succeeded (CrashID above)
04:57:36 at-spi2-registryd disabled a second unresponsive application
04:57:38 Last journal entry before the forced reset
04:58:07 Next boot began; journals were reported as uncleanly shut down
The game was still present in Steam's game-process tracking log when the previous boot ended. I found no game exit, Wine/DXVK/Proton error, relevant coredump, kernel panic, OOM event, watchdog lockup, NVIDIA Xid, i915 GPU hang/reset/fault, or orderly shutdown in that boot. There was also no systemd-sleep suspend/resume sequence. A PROTON_LOG=1 log was not enabled for this one-time occurrence, so I cannot rule out the Proton/game path solely from the absence of a Proton log.
The active Steam CEF GPU reported Intel UHD 630 / Mesa / X11, while Steam's Vulkan/default game GPU was the NVIDIA card. This hybrid display/render path may be relevant.
Possibly related reports found while checking for duplicates:
Proton #9015 reports only the game becoming unresponsive after monitor blanking on Proton 10/KDE Wayland, whereas this event affected the X11 desktop and produced a Steam-client stall: https://github.com/ValveSoftware/Proton/issues/9015
Could the uploaded minidump show whether Steam was blocked in X11/CEF/overlay handling, or whether the Steam stall was secondary to an xfwm4/Xorg hang?
Steps for reproducing this issue
This is the observed sequence, not yet a reliable reproduction:
On Xfce 4.20/X11 with the Intel-display + NVIDIA-render hybrid setup above, start EZ2ON REBOOT : R through Proton Hotfix with the Steam overlay enabled.
Leave the game running and let xfce4-screensaver enter its idle lock/blank state.
Unlock the session.
The graphical session becomes unresponsive; in this occurrence it did not recover within at least one minute and required a forced reset.
Your system information
1785799196(stable, built 2026-08-03)7.1.5-arch1-2, systemd261.2i915, Mesa26.1.6), HDMI-2 at 1920x1080 120 Hznvidia-open 610.43.03xfwm4 4.20.0(compositor enabled,unredirect_overlays=true)xfce4-screensaver 4.20.2xfce4-settings 4.20.5xfce4-session 4.20.421.1.241477590, build ID248356041785421027 hotfix-202607304.0.20260805.254769Please describe your issue in as much detail as possible
Expected: after the Xfce screensaver locks/blanks the display, unlocking should return to the running game and responsive desktop.
Actual: I left EZ2ON running through Proton Hotfix and the Xfce session entered its idle lock/blank state. Immediately after unlocking, the graphical session appeared completely unresponsive. I waited for at least one minute and then forced a hardware reset. I did not try switching to a VT or connecting over SSH before resetting.
This is the first time I have seen the issue and I have not deliberately retried it because recovery required a hard reset.
The previous-boot journal and Steam logs show that this was not a normal system suspend/resume. Background userspace services continued logging for about 75 seconds after the unlock, until the forced reset, so the kernel and at least part of userspace were still alive while the X11 desktop was unresponsive.
Steam's CEF GPU process exited after the unlock, then Steam asserted that its main loop had been stalled for more than 15 seconds. Steam uploaded the corresponding minidump successfully:
Timeline from the previous boot (KST, UTC+09:00):
The game was still present in Steam's game-process tracking log when the previous boot ended. I found no game exit, Wine/DXVK/Proton error, relevant coredump, kernel panic, OOM event, watchdog lockup, NVIDIA Xid, i915 GPU hang/reset/fault, or orderly shutdown in that boot. There was also no
systemd-sleepsuspend/resume sequence. APROTON_LOG=1log was not enabled for this one-time occurrence, so I cannot rule out the Proton/game path solely from the absence of a Proton log.The active Steam CEF GPU reported Intel UHD 630 / Mesa / X11, while Steam's Vulkan/default game GPU was the NVIDIA card. This hybrid display/render path may be relevant.
Possibly related reports found while checking for duplicates:
steamwebhelper: https://github.com/ValveSoftware/steam-for-linux/issues/10495Could the uploaded minidump show whether Steam was blocked in X11/CEF/overlay handling, or whether the Steam stall was secondary to an xfwm4/Xorg hang?
Steps for reproducing this issue
This is the observed sequence, not yet a reliable reproduction:
xfce4-screensaverenter its idle lock/blank state.