181
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 24 Jan 2026
181 points (96.4% liked)
Linux Gaming
24019 readers
271 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:
- Linux Gaming wiki
- Gaming on Linux
- ProtonDB
- Lutris
- PCGamingWiki
- LibreGameWiki
- Boiling Steam
- Phoronix
- Linux VR Adventures
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS


It's definitely a waste of time that he should have stopped after the first one or two where they obviously weren't working.
I still think it's an important demonstration of where things could (and should) be made clearer to the end user.
Like a lot of technical stuff, there's kind of an absurd expectation that caveats can be completely omitted and it's on the end user to figure out. I make tons of documentation at my job as a sysadmin. I get that you can't possibly catalog every edge case and caveat, but from what I can tell, this issue with the Bazzite images was known and happens often enough that the cause is well known. It's a failing by the maintainers that they don't have a basic warning mechanism built in for this scenario.
A warning on the download page. A warning in the updater. Better controls in the release tools so the nVidia release can stay on the last supported version until the new drivers work.
Anything besides just expecting the end user to magically know that the thing labelled as working for their situation does not in fact work at the moment.