Skip to content

fix: resolve real HOME path for Steam shortcuts on OSTree distros - #258

Merged
lobinuxsoft merged 6 commits into
masterfrom
development
Sep 13, 2026
Merged

lobinuxsoft merged 6 commits into
masterfrom
development

Conversation

@lobinuxsoft

Copy link
Copy Markdown
Owner

Fixes shortcuts created by the Agent failing to launch under Steam on OSTree/atomic distros (Bazzite, Anatase), where /home is a symlink to /var/home that Steam's sandboxed runtime doesn't resolve.

  • fix(agent): resolve real HOME path before building shortcut paths (fix(agent): resolve real HOME path before building shortcut paths #255)
  • fix(decky): bump submodule to v1.2.2, which carries the equivalent fix for the Decky plugin (decky-capydeploy#36)
  • fix(hub-connection), fix(agent-server): unrelated pre-existing clippy result_large_err failures cleared along the way

/home is a symlink to /var/home on OSTree/atomic distros (Bazzite,
Anatase). Steam's sandboxed runtime (pressure-vessel) does not follow
that symlink, so a shortcut written under /home/user/... fails to
launch: the Steam client logs chdir "/home/user/..." failed, errno 2
and the game never starts, even though the path resolves fine outside
the sandbox.

Closes #254
result_large_err on WsError::Ws (boxed the tungstenite::Error variant)
and for_kv_map in cancel_all_reconnects. Both were failing CI on this
branch independently of the shortcut-path fix.
…lint

Same pre-existing clippy failure as hub-connection, missed locally
because incremental clippy cache had this crate marked clean from a
prior run. Verified this time with a clean --target-dir.
…reaks-steam-sandbox-on-ostree-distros-home-symlink

fix(agent): resolve real HOME path before building shortcut paths
Includes the shortcut-path symlink fix (decky-capydeploy#36): Steam
shortcuts now resolve /home through /var/home on OSTree/atomic distros
before writing Exe/StartDir.

Closes #256
…e-to-v122

fix(decky): bump submodule to v1.2.2
@lobinuxsoft
lobinuxsoft merged commit fca0d2f into master Sep 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant