-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Background Game Recording while in gamescope-session often crashes the client after quitting games #11498
Comments
Seems to happen to me 100% of the time on SteamOS staging, maybe some other package version that hasn't made it to Stable/Preview/Main yet that's present on staging and upstream Arch. Can rule out Mesa since downgrading to SteamOS' Mesa version makes no difference. |
I seem to be able to avoid a full Steam client crash even with the driver deadlock warning if I add logs with debugging verbosity + `-debug_steamapi`
|
Thanks for the report. There’s a fix queued up on the client side. It won’t be directly on the next beta, but probably the one after that. |
Your system information
Please describe your issue in as much detail as possible:
When Game Recording in the background is enabled within the Steam client, and gamescope-session is in use, quitting games will often lead to an apparent driver deadlock that restarts the Steam client. So far, I've had it happen twice on SteamOS Main on my Steam Deck OLED, and then it happens far more frequently on my ROG Ally currently running CachyOS (Arch Linux).
The ROG Ally runs a much newer Mesa than SteamOS, but other than that I tested the same exact gamescope and Steam client versions across both devices. I've also seen reports from elsewhere about this issue on non-SteamOS distros: ublue-os/bazzite#1862. When I did experience the same Steam crash on SteamOS Main, console output looked identical to the logging above.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: