cc @smcv
This is expected, right now: we don't have a place to put it where it will be in the Launch Options' PATH. steamrt/tasks#669 is relevant.
A workaround is to put bin/launch-options.sh and bin/launch-options.py from https://gitlab.steamos.cloud/steamrt/steam-runtime-tools in some convenient directory (perhaps ~/tmp), and use launch options like ~/tmp/launch-options.sh -- %command%. (This is how we test proposed changes to steam-runtime-launch-options.)
s-r-l-o is a developer tool rather than something that is intended to be user-facing.
This should be fixed in beta ≥ 1780965181, I think?
This should be fixed in beta ≥ 1780965181, I think?
Yes, it is. I re-tested with the latest beta.
In particular $STEAM_RUNTIME_STEAMRT/bin seems to be prepended to the PATH variable in the SteamRT3 environment.
Closing the issue.
Your system information
Please describe your issue in as much detail as possible:
Games should launch when Launch Options are set to
steam-runtime-launch-options -- %command%.Steps for reproducing this issue:
Use experimental SteamRT3 Steam Clientsteam-runtime-launch-options -- %command%The game does not launch, specifically, the
steam-runtime-launch-optionsUI never shows up and the Play button in the Steam Client UI becomes green again.I executed Steam with the following command line:
In the logs I can see this:
Also, possibly related,
Help -> System Reportshows an empty report:apparently because
steam-runtime-launch-clientcannot be found either:This seems to be be different from https://github.com/ValveSoftware/steam-for-linux/issues/13008 (internal task steamrt/tasks#954) and https://github.com/ValveSoftware/steam-for-linux/issues/13012
Thanks, Antonio