42
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Mar 2026
42 points (100.0% liked)
PC Gaming
14191 readers
469 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
Maybe I just got unlucky but running an update today absolutely borked my Steam Deck running this build. Been running it smooth for a few months now, but after updating today I couldn't launch anything in game mode, proton or native. Worked fine in desktop mode, and if I let things sit for 5+ minutes in game mode they'd eventually launch sometimes. Spent a few hours trying to fix it until I just said fuck it, wiped the thing, and went back to SteamOS.
I swear by CachyOS for my desktop, but the handheld edition has given me more trouble than is worth, at least on the deck.
Edit: Opted for a fresh install before totally giving up and it seems to be fine now. Very bizarre but that's just how it goes sometimes
Edit edit: Nope, happening again. Seemed to work out of the box, but after customizing a bit and installing a bunch of junk in desktop mode, it seems to be doing the exact same thing again. Figured it might be Decky Loader, but it still keeps happening with Decky uninstalled (tested before the wipe too). No idea, might see if I can try a different gamescope-session package
Triple edit: Figured it out. The new gamescope session package doesn't play nice with Steam's Background Recording feature. Turning recording off completely fixed this for the time being.