fix: fall back to Valve's stable Steam client when the beta one keeps failing

The native arm64 client follows steamdeck_publicbeta, so a Valve beta
regression reaches every user at once. If the repaired beta client is still
started twice without being shown, or the beta manifest carries no arm64
client, droiddeck-steam-install now installs steamdeck_stable, keeps it, and
logs why (listing the manifest's blocks in the second case). The session asks
the installer for the channel, so -clientbeta and package/beta stay in sync.
BL_STEAM_CHANNEL or ~/.config/droiddeck/steam-channel (beta|stable) pins it.

Valve's 2026-10-15 beta moved the x86 client into a Steam Runtime container.
In case the arm64 client follows, its session now exports
STEAM_STEAMRT_RECURSION_GUARD=1 and, only if steamrtarm64 carries pv-runtime
or a steam-runtime-check-requirements probe, starts it through the same
steamrt shim the x86-64 client uses (now droiddeck-steamrt-shim) and logs it.
This commit is contained in:
ovurrsl authored and Kurt Himebauch committed 2026-10-23 12:03:41 -04:00
1 parent b88eebe09b
commit 7aeb7779bb
9 files changed
+379 -65

No files matched your search

+42
View File
@@ -0,0 +1,42 @@
# Native arm64 Steam client: channel and runtime
The default client is Valve's arm64 Linux build (`steamrtarm64/steam`). Valve does not support it, but
publishes it on the Steam Deck client channels. `droiddeck-steam-install` installs it and
`droiddeck-session` starts it with `STEAM_RUNTIME=1`.
## Channel
- The default is `steamdeck_publicbeta` (manifest `steam_client_steamdeck_publicbeta_linuxarm64`).
Valve also publishes `steam_client_steamdeck_stable_linuxarm64`.
- `droiddeck-steam-install --channel` prints the channel in use. The session passes that value as
`-clientbeta` and writes it to `package/beta`. The two must match, or the client loops on rc 42.
- Setting: `BL_STEAM_CHANNEL`, otherwise `~/.config/droiddeck/steam-channel`, set to `beta` or
`stable`. A set channel never changes on its own.
- With no setting, the client falls back to `steamdeck_stable` automatically. It stays on stable
(`package/droiddeck-channel`) until a setting says otherwise. The fallback happens:
- when the client was started two more times without being shown after the start-failure repair
(`package/droiddeck-unconfirmed`: two unconfirmed starts trigger a repair, which writes
`repaired`; two more unconfirmed starts trigger the fallback);
- when the beta manifest has no `*_linuxarm64_linuxarm64` component. The install log then lists the
manifest's block names, so a renamed or removed arm64 build can be seen.
- The x86-64 client keeps `steamdeck_publicbeta` (see [x86-64-steam-client.md](x86-64-steam-client.md)).
## Steam Runtime container
Valve's 2026-10-15 beta made the x86 Linux client 64-bit and put it in a Steam Runtime container
(pressure-vessel). The container needs unprivileged user and mount namespaces and a D-Bus session bus,
which an Android app does not have. The x86-64 path already works around this. The arm64 client gets the
same treatment if Valve containerizes it too:
- `STEAM_STEAMRT_RECURSION_GUARD=1` is exported for both clients. It tells the client that it is
already inside its container, so after an update it does not re-execute itself through
`pressure-vessel-wrap` (bwrap).
- `droiddeck-steamrt-shim <client dir> <shim dir>` builds the shim when the client carries
`pv-runtime/steam-runtime-steamrt` or a `steam-runtime-check-requirements` probe:
- Valve's runtime is linked file by file;
- the probe is replaced with `exit 0`;
- its own `steam-runtime-launch-client` runs commands directly.
For the arm64 client the session then starts it with `STEAM_RUNTIME_STEAMRT` and `PATH` pointing
at `~/.droiddeck-steamrt-shim` and logs "Valve containerized the arm64 Steam client". Without those
files the shim is not built and the start is unchanged.