protonscr

[General] - Steam client update/bootstrap reset process can hang in Game Mode on Legion Go S

steamclosed Distro Family: SteamOS
ValveSoftware/steam-for-linux#12036 · opened 2025-05-21 by matte-schwartz · updated 2025-06-03 · 3 comments · github
Mmatte-schwartz 2025-05-21 github

Your system information

  • Steam client version (build number or date): 1747772770
  • Distribution (e.g. Ubuntu): SteamOS
  • Opted into Steam client beta?: Yes
  • Have you checked for system updates?: Yes
  • Steam Logs: go-s-update-hang.tar.gz
  • GPU: AMD Z2 Go [Rembrandt APU]

Please describe your issue in as much detail as possible:

Sometimes when my Steam client updates in gamescope-session, or when the bootstrap resets itself from within gamescope-session, the update will hang on:

[2025-05-21 15:21:27] [2025-05-21 15:21:27] Extracting package...
[2025-05-21 15:22:38] [2025-05-21 15:22:38] Installing update...

for 10+ minutes:

Image

with no activity in my steam logs if I watch the directory. If I steamos-session-select plasma and let the Steam client boot up there, the entire update process only takes 30 seconds at most.

In my logs, the period I was stuck on that screen was between 15:21:27 and ~15:34:00 before I gave up and switched to desktop via ssh. At this point, you can see the Steam client completes the update and runtime configuration via the Desktop client in ~45 seconds.

Steps for reproducing this issue:

  1. Trigger a bootstrap reset from within Game Mode (this is the most consistent hang)
    or
  2. Trigger a normal Steam client update from within Game Mode (this is a bit less common)
Oolib14 2025-05-22 github

I have seen this a few times myself — generally if it takes suspiciously long I would do a hard shutdown and things would be fine after.

Llostgoat 2025-06-03 github

There was a bug that could cause the installing step to take longer than expected in some cases. This has been fixed in the latest update.

Mmatte-schwartz 2025-06-03 github

Thanks Andres, haven't been able to reproduce the issue again with the latest client. Going to close as fixed.

Nothing extracted yet.