Host libraries not working

[XakepSDK]

Your system information

• Steam client version (build number or date): Nov 7 2019, at 23:57:46
• Distribution (e.g. Ubuntu): Arch Linux
• Opted into Steam client beta?: [Yes/No] Yes
• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Can't start Counter-Strike 1.6 with system libraries

Steps for reproducing this issue:

1. Start steam with PRESSURE_VESSEL_WRAP_GUI=1 STEAM_RUNTIME_CONTAINER_TEST=1 steam
2. Set SLR compat. tool for CS 1.6
3. Start CS 1.6
4. Select None (use host system)
5. Click run Game does not start.

[XakepSDK]

System info https://gist.github.com/XakepSDK/bba084464f8159d34ef06be43daee3bb

[smcv]

Using only system libraries will not usually work: there is no guarantee that all the libraries in the Steam Runtime exist on your host system (and some of them almost certainly don't).

It's in the test UI to make it possible to try it, rather than because it's expected to be usable.

[XakepSDK]

1. Install steam-native-runtime
2. Install lib32-libva(https://bugs.archlinux.org/task/64445)
3. Run steam-native
4. Run CS 1.6
5. Game works

(--just-divider-to-workaround-broken-github-markdown-parser--)

1. Run PRESSURE_VESSEL_WRAP_GUI=1 STEAM_RUNTIME_CONTAINER_TEST=1 steam
2. Start CS 1.6, select host libs
3. Game does not work Steam output https://gist.github.com/XakepSDK/bc0496cb87967fa3bf5b142be5495d6b

I'm not sure if arch's steam-native script works same as pressure-vessel with host libs.

steam-native script provided by steam-native-runtime package. Script src: https://gist.github.com/XakepSDK/bcbd204782f84b2fa36844f238b0e06b

[smcv]

I'm not sure if arch's steam-native script works same as pressure-vessel with host libs

Approximately, but pressure-vessel doesn't have any special workarounds for host libraries that might be incompatible with Steam Runtime 1 'scout'.

Neither steam-native nor "None (use host system)" will work in general, although they might work for some games.

[smcv]

Actually, I was misremembering what "None (use host system)" is meant to do...

It's meant to set up the container using the host system libraries, but then overlay the Steam Runtime onto it - so it should (if all goes well) use exactly the same libraries that would have been used without SteamLinuxRuntime, including the same LD_LIBRARY_PATH that's used to run the Steam client itself. This helps to narrow down whether putting the game in a container (but not changing the libraries) is breaking it.

There was a bug in the original SteamLinuxRuntime release which I think was breaking this for you. It should be fixed in pressure-vessel 0.20191115.0 (see SteamLinuxRuntime/pressure-vessel/metadata/VERSION.txt or SteamLinuxRuntime/pressure-vessel/bin/pressure-vessel-wrap --help to check which version you have).

[XakepSDK]

./run-in-scout -- pressure-vessel/bin/pressure-vessel-wrap --version
pressure-vessel-locale-gen: No locales need to be generated
pressure-vessel version 0.20190927.0+4+gb7ad27a+srt1

Looks like not published yet

[XakepSDK]

/run-in-scout -- pressure-vessel/bin/pressure-vessel-wrap --version
pressure-vessel-locale-gen: No locales need to be generated
pressure-vessel/bin/pressure-vessel-wrap:
 Package: pressure-vessel
 Version: 0.20191115.0-0+steamrt1.1+srt1

None(host libs): https://gist.github.com/XakepSDK/c9057fc30f5462c98c2e724038aa8732 Scout: https://gist.github.com/XakepSDK/ea1cbe820f00db0e5e92fdc93e7a9cb1 System info: https://gist.github.com/XakepSDK/165ca037fbbd19ee4409b19153e7ed49

Scout runtime does not work now, it worked before.

[TTimo]

It seems likely that the System Info is correct and the container runtime is not installed or corrupted. So let's get https://github.com/ValveSoftware/steam-runtime/issues/204 figured out first.