this post was submitted on 13 Aug 2025
222 points (85.4% liked)

Linux Gaming

20653 readers
126 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:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
monolalia@lemmy.world
222
Gaming on Linux hasn't been great so far... | JayzTwoCents [27:59] (www.youtube.com)
submitted 3 days ago by grue@lemmy.world to c/linux_gaming@lemmy.world
116 comments fedilink hide all child comments
 

Follow-up video to https://lemmy.world/post/32690521

Spoiler alert: the main reason he says the experience "hasn't been great" is because shortly before posting the video his Linux install mysteriously broke and he had no idea why. Therefore, he recommended dual-booting Windows just in case.

Cue sea of comments explaining that the reason for the error he was getting was that Windows screwed up his bootloader (i.e. the problem was caused by dual-booting to begin with, LOL).

you are viewing a single comment's thread
view the rest of the comments
[–] MudMan@fedia.io -2 points 3 days ago (1 children)

I had Fedora bork up on me on each kernel update for a while and force me to rebuild... something. It's been a while, I forget what the underlying issue was.

People like to claim Windows updates are more problematic than Linux updates because they install without permission, but it's not really true. For one thing, Bazzite updates in the background just like Windows does (it just does it on user reboot as opposed to forcing a reboot).

[–] Agility0971@lemmy.world 2 points 3 days ago (1 children)

What is your point?

[–] MudMan@fedia.io -3 points 3 days ago

That this is type of issue is relatively familiar territory, at least in Fedora-based distros. I can't promise it's the exact same known issue I encountered in the past, but it sure seems similar.