as the title says, I’ve been trying to find a fix, but nothing I’ve done works. when i leave my pc sleeping overnight with a game running, next morning after turning the pc on, Steam just closes for no reason, and any game I left running, shuts down (obviously, because it doesn’t detect steam running). I’ve tried everything I could, but simply doesn’t work, and I haven’t found anyone having the same problem when I searched on google. One of the main reasons I switched to bazzite was the quick resume for games, but this problem is stopping me from fully enjoying bazzite.
I read somewhere that it may have something to do with the fact that after 30 mins of setting the pc to sleep, bazzite automatically enters hibernation, which is the reason steam stops working. I haven’t been able to find any fix to that behavior (neither I know if it’s the reason, but it’s the only hint I have for now). Anyone having the same issue? please help me find a fix. Bazzite is great, and I don’t want to go back to windows (specially because windows is not good when it comes to resuming games from sleep). I only use bazzite on desktop mode.
my specs:
RTX 4060TI 16GB VRAM
RYZEN 5 3600
32GB RAM
500GB SSD SATA
1TB NVME M2 (bazzite and steam are installed on this disk)
1.5TB HDD
PSU 650W 80+ BRONZE
4 SCREENS, ALL OF THEM 1080P (2 connected through display port, 2 through HDMI)
Bazzite and steam are updated to the latest version. I only play with wifi connected to ethernet, my pc doesn’t have a wifi receiver.
I also have a dual booting for windows, but I only use it for work. I don’t think that’s relevant, but anyways I leave the info in case it’s necessary.
Please help!
Do you see error messages?
journalctl -xe
journalctl –since yesterday
or presumably journalctl –since today suffices if it happens after wake up.
One of the main reasons I switched to bazzite was the quick resume for games, but this problem is stopping me from fully enjoying bazzite.
I’m not quite sure what you mean by “quick resume for games.” Resume from what?
I’m also having trouble understanding why you would want to leave the game running over night. Is this a common use-case scenario? Can’t you just save your progress, close the game, and launch it again when you’re ready to play?
Disclaimer: My inability to understand your use-case is possibly my own shortcoming – not that you’re wrong to want to do that.
no, steam closes with no error messages at all. It just closes, also this time was even worse. When I turned the pc on, it didn’t show anything at all. Complete black screen, had to do a full reset.
this is what i got with the command on the terminal
mar 09 10:43:46 bazzite rpm-ostree[5727]: client(id:cli dbus:1.220 unit:app-org.kde.konsole-5642.scope uid:10>
mar 09 10:43:46 bazzite rpm-ostree[5727]: In idle state; will auto-exit in 63 seconds
mar 09 10:43:50 bazzite konsole[5642]: Process 5652 did not die with SIGHUP
mar 09 10:43:56 bazzite systemd[1831]: Started app-org.kde.konsole@727e0a6085b94a139156d9a240bb76f2.service →
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: systemd-devel Info Page
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 572.
mar 09 10:43:57 bazzite systemd[1831]: Started app-org.kde.konsole-5855.scope.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: systemd-devel Info Page
░░
░░ A start job for unit UNIT has finished successfully.
░░
░░ The job identifier is 589.
mar 09 10:43:57 bazzite rpm-ostree[5727]: Allowing active client :1.223 (uid 1000)
mar 09 10:43:57 bazzite rpm-ostree[5727]: client(id:cli dbus:1.223 unit:app-org.kde.konsole-5855.scope uid:10>
mar 09 10:43:57 bazzite rpm-ostree[5727]: client(id:cli dbus:1.223 unit:app-org.kde.konsole-5855.scope uid:10>
mar 09 10:43:57 bazzite rpm-ostree[5727]: In idle state; will auto-exit in 64 seconds
mar 09 10:43:57 bazzite rpm-ostree[5727]: Allowing active client :1.225 (uid 1000)
mar 09 10:43:57 bazzite rpm-ostree[5727]: client(id:cli dbus:1.225 unit:app-org.kde.konsole-5855.scope uid:10>
mar 09 10:43:57 bazzite rpm-ostree[5727]: client(id:cli dbus:1.225 unit:app-org.kde.konsole-5855.scope uid:10>
mar 09 10:43:57 bazzite rpm-ostree[5727]: In idle state; will auto-exit in 63 seconds
For quick resume, I mean like resuming the game right where you left it after turning the pc on, kind of similar to what you can do on a handheld (like steamdeck) or on a console (like ps5).
I’m kind of bussy in very intermitent times because of my job, and lots of games completely reset progress from misions when I just save and then return, for instance, in RDR2 sometimes you find NPCs over the world and you can start helping them, but the game won’t save until you complete that event, thus if I got to go because of my job and return next morning, I can’t close the game, or I will completely lose the game event, and since those events are completely random, if I choose to close the game during that moment, when I open the game again it won’t happen again, maybe ever.
And I don’t want to leave the pc on at all times, since my electricity bill is already vey high (lol)
I switched to bazzite, because everyone said it was THE OS for quick resuming games (that’s why lots of people use it on handhelds that come with windows, like the ROG xbox ally X, since windows does a terrible job at resuming games when you put the handheld to sleep), and from what I read it worked awesome on pc as well.
btw, english is not my main language so, sorry if I sound rude.
1 Like
Ah, I see now. Yeah, I don’t use the Steam Deck or any handhelds so I couldn’t see why that would be a sought-after feature. I’m sure there’s a whole world of use-cases that I don’t even think about because it doesn’t impact me. Thanks for the clarification.
btw, english is not my main language so, sorry if I sound rude.
No worries at all. I didn’t perceive your reply as rude.
I’m sorry I can’t be of much help with this. I hope someone else can help you and that you get it resolved soon.