Linux Gaming

21653 readers

358 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

monolalia@lemmy.world

[help] Game freezing in Nobara after update [solved-ish] (lemmy.nz)

submitted 2 weeks ago* (last edited 2 weeks ago) by Dave@lemmy.nz to c/linux_gaming@lemmy.world

13 comments fedilink hide all child comments

I had a previous post about how the game and computer would freeze when using my controller. This is now resolved, the controller no longer freezes the computer, but I'm still getting weird visual artifacts in games, and one game (Assassin's Creed Rogue) is freezing, which seems to be triggered when I enable the eagle vision. I've already played 20 hours without a single crash or issue until this recent system update.

I've got an up to date Nobara installation, using the Gnome version. Nobara is based on Fedora with some gaming related things pre-installed. It's running on an OG Framework laptop, so it's Intel integrated graphics but it has been working great until now.

I'm running Assassin's Creed Rogue through Steam. I have tried running the game using the experimental proton but that didn't help.

Anyone got ideas for further troubleshooting? The best I've got is that it might be shader related, as in Hades the lighting is weird and in Assassin's Creed Rogue it's enabling eagle vision that triggers it to freeze. I have tried disabling the pre-cached shaders and it doesn't help, I've enabled it to trigger re-generation of them but it didn't help.

Any ideas?

Edit: I sort of solved this. It seems to be related to GNOME, when running the KDE Plasma desktop environment it doesn't crash. So I guess I'm using KDE until that gets resolved.

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

[–] Laavu@sopuli.xyz 2 points 2 weeks ago (1 children)

There are basicly two ways to go with regressions: bisecting or research.

With bisecting you restore a working backup, and try to isolate the breaking change. In your case you could try updating one package at time and testing. Since these are often GPU related, start with kernel and mesa. When you find the breaking update, you can either report it on your distros issue tracker, or git bisect it further to the breaking change in the source code to increase the change of it getting fixed quick.

With research, you look into relevant bug reporting databases. These include your distros issue tracker, Valve's issue trackers both for Steam and Proton, DXVK issue tracker, freedesktop.org and kernel issue trackers.

These are a lot of work, so most people just try random stuff. That's why you often get suggestions to do so.

Sorry I don't have an easy fix for you.

[–] Dave@lemmy.nz 1 points 2 weeks ago

Thanks, I went with the trying random stuff option. Not really in the mood to reinstall my distro and restore a backup 😆

With comments from some of the others I ran with the idea that it might not be my distro, and came across recent complains about crashes in GNOME. I then installed Plasma as an alternative, and when I log in to the Plasma DE and run the game from there, it doesn't crash, at least not in the same reliable way that it does in GNOME. Super annoying as I love GNOME haha, but I guess I'm gonna be running KDE for a while, at least until I'm done with this game.

It's also possible that GNOME on Nobara doesn't get the love it used to. It was the default DE for quite some time, but a year or so back they switched to make KDE the default, with GNOME still offered as an optional version.