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 must log in or # to comment.
You can run steam trough the terminal and you will see what causes the error. But it seems you have had some issues with your install, I would recommend you try another distro.
If you don’t want to try installing Plasma as they handle things differently in the background so it my be more stable.
My distro has been fine for years up to this point. I’ve bounced around others but always come back.
Running Steam through the terminal doesn’t give a whole lot more info, the game just freezes, nothing in the terminal until I click the force close option that pops up. Then it shows:
(process:126826): GLib-GObject-CRITICAL **: 22:15:58.804: g_object_unref: assertion 'G_IS_OBJECT (object)' failedI worked out I can easily install Plasma and switch between DEs, so have done that. The game doesn’t crash on Plasma, so it seems to be GNOME related. Which is a shame because I love GNOME and am not a fan of KDE, but I guess I’ll have to use KDE for a while 😅
Nice nice, I thought as much, sometimes it do be like that. You might be able to disable the compositor for the game itself OR use gamescope, but i have never successfully achieved that.
Turns out it’s not fixed on KDE. It’s just that it randomly lets me play for 5 mins without crashing sometimes.
I’ve tried downgrading graphics drivers, rolling back to a previous kernel, no change 😭
I still get the impression something is wrong with your install, could you try booting from a external drive to a gaming Linux OS? If that still happens maybe something is wrong with your HW.
I don’t have a spare external drive 😭. I tried installing on a flash drive and the game still crashed, but the whole thing was so slow I can’t be sure of the cause.
I tried to create a partition on my drive and install bazzite but apparently it doesn’t like that so I dunno 🤷. I guess I might try installing Mint on the partition and see how that goes.
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.
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.
Hmm, I’m in sequence 6 which is past the point mentioned but I will try to stick out this section without eagle vision to see if it’s actually the game itself. Thanks for the info!
Edit: I tried starting a new game, it’s still an issue. Definitely a new thing after the update 🙁
If you think its shaders relatet try disabling all settings and playing it on minimum graphics settings.
Didn’t help :(
