Hey gang, I’m having trouble running this game. I have a Ryzen 7 7800X3D, RTX 4070 Ti Super, 64GB DDR5 RAM, on a B650 motherboard. My issue is frequent crashing/freezing, meaning I can’t play longer than a few minutes at a time. I have tried re-installing the game, Steam, the entire OS, and then fully wiping the drives to remove Windows dual partition and only installing Mint. Then I was pointed to the drivers, so I tried updating using the ppa(?) driver availability as Mint only offered the nVidia 550 through Driver Manager. I tried each of the separate drivers, rebooting between each load, and still having the same issue. For reference, I was able to run through character creator and early intro of the Streetkid after many failed attempts. But then I get to the ride-along with Dexter DeShawn which does not have skippable sections and takes too long. So the length of that conversation is too long before the game either freezes or outright crashes.
Any suggestions are welcome, it’s really really annoying me and pretty disheartening after hearing how everything just works on Linux (other than competitive online games, which I don’t really play anyway).
Edit to add: I also tried the different Proton versions available through Steam, where I purchased the game.
Okay just tried it again to get a better test. To troubleshoot, I’m starting with nothing and will hopefully only change/monitor 1 thing at a time.
Just booting the PC, opening Steam via Terminal, and playing the game using Proton Experimental selected, it ran for 2m 9s before freezing (my save is right before talking to Padre after leaving the bar for the opening sequence, game freezes during the car ride before I have a chance to save again. I have been able to get past this before, at least enough to make a save on the other side, but this length of time may serve as a good reference for someone.)
Steam has a popup window that reads “steam_app_1091500 is not responding; You may choose to wait a short while for it to continue or force the app to quit entirely.” After about 5 minutes nothing changes, but I can’t even access that popup because it is frozen. I have to CTRL+ALT+Tab to Steam to then click “Stop” there. Here is what the Terminal reads from opening until game force closing:
"[2025-05-01 11:40:55] Nothing to do pid 7527 != 7526, skipping destruction (fork without exec?) Game Recording - game stopped [gameid=1091500] Removing process 7725 for gameID 1091500 Removing process 7707 for gameID 1091500 Removing process 7688 for gameID 1091500 Removing process 7660 for gameID 1091500 Removing process 7639 for gameID 1091500 Removing process 7583 for gameID 1091500 Removing process 7557 for gameID 1091500 Removing process 7544 for gameID 1091500 Removing process 7534 for gameID 1091500 Removing process 7531 for gameID 1091500 Removing process 7529 for gameID 1091500 Removing process 7526 for gameID 1091500 Removing process 7525 for gameID 1091500 Removing process 7524 for gameID 1091500 Removing process 7520 for gameID 1091500 Removing process 7324 for gameID 1091500 Removing process 7323 for gameID 1091500 Removing process 7322 for gameID 1091500 Removing process 7321 for gameID 1091500 Fossilize INFO: Setting autogroup scheduling.
(process:8216): GLib-GObject-CRITICAL **: 11:52:01.198: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed reaping pid: 8216 – gameoverlayui"
Hm this part of the log doesn’t look like the error. Those messages usually show up after the process has crashed. If there is nothing that looks like it’s gamecrash related to you further above in the log, type
sudo dmesg --follow
in a terminal. This display the logs of all device drivers on a kernel level. While that is open, start the game and wait for it to freeze and see if any errors show up.Also, if you post log messages again please put them in a
by typing it like this:
```
codeblock
```
Should be more readable. If the log is rather long just put it into a pastebin or some other text sharing service.
Okay will do. And yes because I had to Force Stop it through steam rather than it crashing on its own I didn’t see any super helpful logs. I will try the command you sent when I am able!
When you run steam from the terminal, you want to use -d to get the debugging info:
I know this is revisiting an old post, I’ve been unable to game for some time. When I try this I don’t get any other information. However, I have seen a lot of other issues system wide that just make it feel unstable. Like when playing I will have system wide freezes not just the game freeze (unable to move mouse/keyboard is unresponsive/etc.), I’ve had issues in Firefox where pages will just freeze or be non-responsive and have to force close the program or again it’s system wide freezes. So I’m pretty sure it’s not Steam related and is just the whole OS. I can’t really get logs because when the system freezes my only option seems to be hard shut down then reboot.
In Steam, add this to the launch options games where you crash in order to enable logging to a text file:
(-from: https://github.com/ValveSoftware/Proton/wiki/Proton-FAQ)
Then there will be a log file of the game in your home directory, named steam-$GAMEID.log.
When you’re reading that log, the error that causes the freeze should be in the end of the log somewhere.
If you just want to log the output of the Steam -d command (if you can’t find a crash in the proton log, for example) you can use tee, explained here since you should not just run random terminal commands you find online without knowing what they do: https://www.geeksforgeeks.org/tee-command-linux-example/
It’ll write the output of steam -d to the terminal so you can read it, and also to the steam.log in your home directory.