Could you give a reference for what numbers may be abnormal/potential failures? So I can keep an eye on them while troubleshooting the issue.
- 1 Post
- 23 Comments
I did try checking the logs but nothing seems to show in terminal for Steam. Are separate logs for each game instance kept somewhere or do I need to live monitor in a terminal somehow while the game is playing?
How do I do that? Also, is there a check to see if this is the issue before doing it?
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!
No, it’s not available through Steam. So far I’ve only tried the Proton versions available in Steam compatibility settings.
I also added the launcher skip command in Steam, and have been running with Proton Experimental (though I have tried many other versions). I am running the version of Steam installed via Mint’s Software Manager, not sure what flatpak is or what it would change.
I also am currently running the following kernel: 6.8.0-58-generic (per the Update Manager).
It was via USB, just not a flash memory stick but rather an external drive.
Okay so if X11 is what fixed it for you, I should stick with X11 it sounds like. Is that correct?
Which Proton Version did you try? I think I’ve been through each of them available on Steam but can retry a specific one to troubleshoot.
Alright I got it installed. This was attempt 2, (Step 1 in another comment basically with no changes to get a baseline).
I installed mangohud and configured to show GPU load, CPU load, VRAM, RAM, GPU temp, and CPU temp. I booted the game again, and this time from pressing Continue and loading into the game, I didn’t even have time to start the timer. I would guess maybe 2s before freezing. Onscreen stats from MangoHUD read “GPU 98%, 53C, CPU 64% 71C, VRAM 7.9GiB, RAM 9.0GiB”.
CPU and GPU both shot way up from the baseline configuration example in GOverlay I used. Looks like this may be the issue. I’ll try to get the temps down and retry.
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"
I do not know what Wayland nor X11 is. I’m running Linux Mint with Cinnamon(?).
Okay I’ll install that to try to get some monitoring in-game. Do you know if that’s available directly through Mint’s Software Manager?
This whole PC is brand new (built earlier this year), so I don’t want to have to replace a component so soon. Especially since it seems to work fine prior to swapping to Mint in general.
I did try to install Bazzite using Ventoy on an external drive, but it wasn’t working. Someone told me I should use a USB flash drive instead of an external hard drive and that may have been the issue, but I’ll keep this in mind if it fails again!
I haven’t been starting steam directly from the terminal but will try this when troubleshooting to read the logs!
Did you do anything special during setup? I couldn’t find many reports specific to this card on ProtonDB, but lots of people were using different Proton versions that weren’t available on Steam so wasn’t sure if that was it.
Okay I’ll give this a shot first to determine if it’s overheating. The air from the case doesn’t feel like it’s too hot coming out, and the game seems to run smoothly with no graphical disturbances until the moment of freezing or crashing, but I’m willing to try it out. I’ll be going through these suggestions one by one hopefully tonight and tomorrow and will try to reply/update as I do so!
WR5@lemmy.worldto World News@lemmy.world•While the world watches Gaza, here is what’s happening in the West BankEnglish3·8 days agoMother lovers
Do homosexuals have some better control over their body temperatures?