Deck unable to go into sleep mode after 3.4

[Cyondris]

After I updated my deck this morning, I noticed that it stays illuminated after putting it into sleep mode, and then "wakes up" about 30 seconds later. I've tried changing to beta and then back to stable, but the issue persists.

Has anyone else seen something similar?

[Honkivore]

I have this problem too
thought it was a borked update, reinstalled steamos via usb disk and it was fixed
issue came back as soon as I reinstalled the update, very frustrating
trying to enter sleep causes a hang on a blank screen for somewhere around 30s, after which it pops back into the main menu
trying to reboot via game mode also hangs indefinitely on "shutting down steam", have to force reset at that point
rebooting from desktop mode works though, but trying to sleep from desktop hangs and recovers

this magically fixed itself right after I made this post lmao
only other thing I did was disable quick boot, and then reboot twice
maybe give that a shot?
shut down, then hold volume up and tap power to get into BIOS
enter setup menu, disable quick boot, save and restart
I forget exactly where the option was but it's in there somewhere

another thing, I just tried reenabling quick boot and it works fine still
maybe it wasn't related, or maybe it shook something loose that's no longer a problem now that it's run some diagnostics
I have no idea, but I hope it fixes this for other people having the issue

[SixStringNinja]

I had the same symptoms while a game update was installing. Once done sleep worked again. Game was Witcher3 and was started before I updated to 3.4.

[Phazon]

I'm having the same problem. It worked fine for a short while after updating to 3.4 Stable, but now I am completely unable to restart, shutdown, or put the device to sleep. The former two hangs at "Shutting down Steam" and the latter turns the screen black but leaves the backlight on. I have to hold the power button and force a shutdown so it doesn't drain the battery. I've tried the different update branches but none of them fixed it.

[LightningMcQueef]

Same here, but it seems to work again. I totally shut down the device, after rebooting from an entirely turned off deck it works.

I believe what six strings ninja is saying about downloading gamss might be plausible. I not only updated the system but just recently installed 2 games I bought on sale.

[Pinqvin]

I have also noticed this issue. First power button press just makes the screen go dark and eventually (20-30 seconds later) I get the PIN entry screen again. After entering my PIN and pushing the power button again, the Deck seems to enter sleep properly.

Trying to reproduce this after a restart, it seems like it isn't happening anymore? Might be related to a game update happening on the background like was mentioned earlier, but at least a game install doesn't seem to trigger this behavior when I was trying to get this issue to happen again. Running OS version 3.4.2, BIOS version F7A0110

[Phazon]

Seems my Deck straightened itself back out? At some point I shut it down and left it alone, and it completed the shutdown process after a long couple of minutes. After that it started shutting down, restarting, and sleeping properly again. I did have a few updates scheduled for download but they weren't actively downloading at the time, so I don't know if that was the cause. I got them out of the way just in case.

[TugBoat TB]

I did have this problem after installing 3.4.2 and all the other issues like not being able to boot a game from my SD unless I physically remounted it. I changed to the preview channel where it updated me to 3.4.3 but I still had all of the problems metioned. However, when I changed back to the stable channel and reinstalled 3.4.2 It fixed everthing.

[Kevman95]

I've had this happen periodically. Not sure why it happens, but every single time it solves itself. Very confusing.

[nice bnuuy]

I have run into this same exact issue and I suspect it may have to do with any game updates that are installing when putting it to sleep. I’ll have to try and recreate it, but the last time I had this happen I noticed the system was still making noise when I touched the dpad. I was able to hold the power button and get the menu to power down normally,

When I selected shutdown, it had to stop the game update process before shutting down. I turned it back on, let it update Elden Ring fully, then it went to sleep just fine, which is really weird.

[Jiggy007]

Any news to this? This started to happen after update 3.4.4 (I think 3.4.2 worked totally fine. I started to notice this at 3.4.4 Update)

[The Asgorian Bugsong]

Noticed it happening again after I turned my steam deck off and on again (it also finished up the shader cache updates), I tried tapping the power button to sleep and it would wake automatically after 30 seconds. Putting the deck to sleep through the menu seemed to do the trick and even made tapping the power button to sleep work afterwards.

[Kevman95]

So i think i figured out why it doesn't put you to sleep:

On the settings in system, when my deck doesn't go to sleep if i scroll to the bottom, it says that the "run storage maintenance task" is in progress. I waited a few after this task was completed, and the deck was able to properly go to sleep. I did not have any downloads running either.

So it doesn't seem to be a bug persay, i would assume this is normal. As if your doing disk operations you wouldn't want the user to put the device asleep while they are being performed. Maybe they could add something to alert the user to the running task so they are aware why the device can't go to sleep.

[The Asgorian Bugsong]

Publicado originalmente por Kevman95:

So i think i figured out why it doesn't put you to sleep:

On the settings in system, when my deck doesn't go to sleep if i scroll to the bottom, it says that the "run storage maintenance task" is in progress. I waited a few after this task was completed, and the deck was able to properly go to sleep. I did not have any downloads running either.

So it doesn't seem to be a bug persay, i would assume this is normal. As if your doing disk operations you wouldn't want the user to put the device asleep while they are being performed. Maybe they could add something to alert the user to the running task so they are aware why the device can't go to sleep.

A warning notice if you try to put your deck to sleep during that would probably sort things out. Would make it better compared to the deck sleeping for 30 seconds, then waking up without any input.

[VeskitPhD]

Publicado originalmente por Kevman95:

So i think i figured out why it doesn't put you to sleep:

On the settings in system, when my deck doesn't go to sleep if i scroll to the bottom, it says that the "run storage maintenance task" is in progress. I waited a few after this task was completed, and the deck was able to properly go to sleep. I did not have any downloads running either.

So it doesn't seem to be a bug persay, i would assume this is normal. As if your doing disk operations you wouldn't want the user to put the device asleep while they are being performed. Maybe they could add something to alert the user to the running task so they are aware why the device can't go to sleep.

I saw just started experiencing this issue and can confirm that the "run storage maintenance task" was greyed out and running. Restarting didn't seem to fix this issue, nor did the "run system maintenance" seem to finish with enough time. I did recall I recently downloaded a new game to my SD card before this issue occurred. I tried launching said game for the first time and exited out once it loaded. Afterward I noticed the "run storage maintenance" showed "run" instead of "running." More importantly, I was finally able to put my deck to sleep without it coming back on. Not sure why this issue arose, the game finished downloading before the sleep issue started. My only hypothesis is steam needed to verify the install before I started frantically forcing the deck to shut down to fix the issue.

[Minneyar]

I did have that issue once, although it went away after a reboot, and I haven't seen it happen again since then.