The only difference here is the user that is logged in.
Only the UI is affected on wake up, the game plays fine after suspend/resume.
My Library shows over 10500 games on the Library tab.
The secondary account has less than 10% of that total, I'd have to check to get the exact number.
Any updates on this issue? It's been a few months and having to wait a minute for the deck to resume from sleep is annoying.
Only workaround I've found is to keep the deck offline before and when resuming from sleep. However the client hangs again when connecting back to wifi.
I actually figured out that this was partly due to having a large amount of dynamic collections -- I was able to increase performance by removing all of my dynamic collections and most of my static ones as well. However, in recent updates, my Steam Deck has started having full system lag on wakeup instead of just having the UI be unresponsive and I haven't found a workaround for that yet.
@barryjj THANK YOU!!! I had over 2 dozen dynamic collections and removing those reduced the starting lag from almost a minute to just a few seconds.
I have the same issue with my Steam Deck. The UI generally seems to get blocked during synchronizations with a Steam account. After waking up the Steam Deck the UI appears and is freezed up to two minutes (I have over 200 dynamic collections). If the internet connection is disabled, the Steam Deck UI is usable immediately after waking up.
Nothing extracted yet.
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Should happen:
Pressing resume should cause the unit to wake up and resume where left off. If pressing anything that causes the UI to need to display or update, it should do so in a timely manner.
Does happen:
Pressing the resume button wakes the unit and the display is active. Games currently suspended will work normally and inputs will be read. Anything that involves the Steam UI, however, freezes. Buttons like volume +/-, Steam, QAM can be mashed and nothing will happen. If you are in the Steam UI looking at your library, all inputs will be essentially buffered or sent to /dev/null and the UI will become unresponsive. For example, in game, if you press the volume buttons, the UI slider for volume will not display but the volume will change.
Note:
I've tried another account on the same Deck and it doesn't experience the same issue. The secondary account has < 1000 games. My account has over 9000 games, maybe even over 10k. This seems to be related to the size of the user's library and like Steam gets hung for the 30-60s cause it's trying to reprocess some library information and hangs until it does.
Steps for reproducing this issue: