this post was submitted on 30 Apr 2025
43 points (100.0% liked)
Linux Gaming
18417 readers
168 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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: