Linux Gaming

18950 readers

35 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

No memes/shitposts/low-effort posts, please.

Resources

WWW:

Discord:

IRC:

Gaming on Linux

Matrix:

Telegram:

Gaming on Linux

founded 2 years ago

MODERATORS

[email protected]

System needs to be updated for steam to work. Advice? (lemmy.dbzer0.com)

submitted 4 days ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

Fedora workstation 42. Steam flatpak. Same behavior no matter which proton I use. 4090 using the rpm fusion team’s package

Behavior: I boot up. I fire off a game from steam flatpak. Game 100% worked fine yesterday. Today something updated, so I get “processing vulkan shaders” let it finish. Game starts - slow af. Game works, but it’s like the video card isn’t there, and the game is using my CPU’s integrated GPU (I literally think this is what’s happening). The settings are way too high so it’s a lag fest - if I turn them way down, everything is fine (at 320x200 LOL)

Ok so here’s the fix. I update the system. That’s it. Update, reboot, everything works perfectly. (Interestingly, vulkan shaders need to be processed again). My question is WHY? Shouldn’t I be able to not update and things still work? I’m not talking like I haven’t updated in years. Sometimes it happens within days. It’s not the end of the world - I was going to update anyways - but it’s annoying.

Any thoughts on what to check and maybe tweak? Thanks.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 4 days ago

Yeah, definitely do this. Getting half a system update can cause all kinds of weird problems.

It can also be that NVIDIA cards have issue with different power states. My card will forget that it is connected to HDMI if it is idle for too long. It's entirely possible that the card just hibernated and the flatpak container removed it and failed to re-add it leading to CPU rendering, a reboot will fix this (which OP did as part of a system update).

You could fix it without a reboot, but that would require you digging into the problem a bit more. In my case, I wrote a script that re-set the display properties and that caused the DE to attempt to use the card again. I have it bound to a hotkey so if my display doesn't turn on, I can just press a button (instead of rebooting).