Open MatthijsMarco opened 2 weeks ago
Can sign that one. Have the Same Issue for weeks now.
Strangely, the problem seems to have fixed itself a few days ago (I didn't notice, but my girlfriend said she used our HTPC and never even knew it was an issue, which was quite funny). This is the second time I've had this bug (should have mentioned that in the original post, sorry). Last time I thought one of my troubleshooting steps helped, but now I'm unsure. Since it isn't the first time and someone else also had the issue now, I'll leave the issue open for now.
Alright everyone, get your voodoo dolls and detective hats out, because we have a curse to investigate: after applying the fix script to be able to receive updates again, the issue reappeared! I'm genuinely stumped, and quite annoyed.
I had to completely reinstall Bazzite to get rid of it. Not even Rebasing solved it. I could also rule out Decky and all its Plugin as it also happened with Decky removed.
I managed to fix it! (Sorry that I found it too late for you, @NightHammer1000 ) This thread describes the issue for Steam Deck.
For Bazzite:
sudo mkdir -p /etc/systemd
sudo nano /etc/systemd/coredump.conf
rm -rf /home/deck/.local/share/Steam/compatibilitytools.d/*
rm -rf /home/deck/.local/share/Steam/steamapps/compatdata/0
Considering how many people are complaining about this issue without a fix, I'm surprised how far I had to scroll to find someone with an actual solution (4th or 5th page of Google). While the issue itself is now resolved, I'd like a dev's comment on if a preventative fix can be applied to avoid this issue in the future. Afterwards the issue can be closed.
Describe the bug
When attempting to shutdown or reboot the system from the Game Mode UI, the system hangs on the "Shutting down Steam" screen.
What did you expect to happen?
A successful shutdown or reboot.
Output of
rpm-ostree status
Hardware
Extra information or context
There seems to be a zombie process:
It comes from the following parent process:
Which gives he following strace output (ad infinitum):
The process mentioned in the strace output (6511) doesn't seem to exist:
But, for some reason, sending a kill command to the phantom process successfully continues the shutdown process: