On OSTree/atomic distros (Bazzite, Anatase) /home is a symlink to /var/home. Steam's sandboxed runtime (pressure-vessel) does not resolve that symlink, so a shortcut written with Exe/StartDir under /home/user/... fails to launch — the Steam client itself logs chdir "/home/user/..." failed, errno 2 and the game never starts, even though the same path resolves fine outside the sandbox.
Confirmed on an OneXFly F1 Pro running Anatase: a game installed via CapyDeploy to ~/Games/<name> got a shortcut pointing at /home/lobby/..., and every real Steam launch attempt failed with that chdir error while manually launching the binary (resolving the path myself) worked fine.
Fix: get_user_home() in steam_utils.py must resolve the real path (os.path.realpath) before it's used to build shortcut paths, not just return the literal /home/... string.
On OSTree/atomic distros (Bazzite, Anatase)
/homeis a symlink to/var/home. Steam's sandboxed runtime (pressure-vessel) does not resolve that symlink, so a shortcut written withExe/StartDirunder/home/user/...fails to launch — the Steam client itself logschdir "/home/user/..." failed, errno 2and the game never starts, even though the same path resolves fine outside the sandbox.Confirmed on an OneXFly F1 Pro running Anatase: a game installed via CapyDeploy to
~/Games/<name>got a shortcut pointing at/home/lobby/..., and every real Steam launch attempt failed with that chdir error while manually launching the binary (resolving the path myself) worked fine.Fix:
get_user_home()insteam_utils.pymust resolve the real path (os.path.realpath) before it's used to build shortcut paths, not just return the literal/home/...string.