- Jan 05, 2021
-
-
Ludovico de Nittis authored
Improve logging See merge request steamlinuxruntime!27
-
Simon McVittie authored
It's distracting to see messages about gameoverlayrenderer all over the place. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This will be enabled if we are writing a log. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
_v2-entry-point: Add support for pressure vessel log file See merge request steamlinuxruntime!26
-
- Jan 04, 2021
-
-
Ludovico de Nittis authored
With this change it should be easier for users to gather the necessary logs when filing an issue report. They can now just launch Steam with "STEAM_LINUX_RUNTIME_LOG=1", and optionally also "STEAM_LINUX_RUNTIME_VERBOSE=1", and a log file will be created in their Scout/Soldier install directory. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
With the new "STEAM_LINUX_RUNTIME_VERBOSE" it should be more clear that we are enabling the verbose logs for all the Steam Linux Runtime components, instead of just pressure-vessel. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Dec 10, 2020
-
-
Ludovico de Nittis authored
Improve error behaviour See merge request steamlinuxruntime!25
-
Ludovico de Nittis authored
run-in-steamrt: If run inside Flatpak, don't force copy mode forever See merge request steamlinuxruntime!24
-
Simon McVittie authored
This creates a lot of noise on stderr if we're in verbose mode, but is not actually useful. By silencing it, we can have the actual problem appear more prominently. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
If starting the container failed the first time we tried it, there's no point in trying again repeatedly. Unfortunately, when Steam runs setup commands, it ignores their exit status, so we can't make it give up early. Because the main game runs in a slightly different environment, it's possible that it might succeed even when setup commands fail, and it's also possible that launch options are making it more verbose or debuggable, so try harder to start that one. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Dec 07, 2020
-
-
Simon McVittie authored
When sharing a Steam library directory between Flatpak and non-Flatpak instances of Steam, just because we have to activate PRESSURE_VESSEL_COPY_RUNTIME_INTO for Flatpak, that doesn't necessarily mean we want to do the same in the non-Flatpak case. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Dec 04, 2020
-
-
Simon McVittie authored
Optionally shut down and relaunch container See merge request steamlinuxruntime!23
-
- Dec 03, 2020
-
-
Simon McVittie authored
The waitforexitandrun verb is the first opportunity we get to know what our final environment variables are. It's also the first time we get run under "adverb" wrappers, if any, such as taskset. Proton uses a single set of Wine services to run the setup commands, then shuts them down and relaunches everything for the actual game; we can do similarly here. However, the startup time cost of doing this could be significant, so it's currently off by default so that we can experiment with it. Run with PRESSURE_VESSEL_RELAUNCH_CONTAINER=1 to try it. Partially addresses steam-runtime#304. Resolves: T25223 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
If we don't find the socket, we are not going to be able to communicate with the launcher, so we had better try to terminate it, print an error message and exit. Partially addresses steam-runtime#300. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This is used for transient copies of the runtime (in some modes) and might be used for logging later. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
deploy-runtime: If available, automatically unpack the debug symbols See merge request steamlinuxruntime!22
-
Ludovico de Nittis authored
This will make it easier to start debugging programs inside the container. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Nov 24, 2020
-
-
Simon McVittie authored
_v2-entry-point: Support custom LD_LIBRARY_PATH from game launch options See merge request steamlinuxruntime!19
-
When a game is launched with a custom launch option as: "LD_LIBRARY_PATH="/my_libs:${LD_LIBRARY_PATH}" %command%" we want to treat /my_libs as if it were part of the OS-level search path. Instead of overloading "SYSTEM_LD_LIBRARY_PATH", this patch introduces a new, more appropriate, environment variable called "PRESSURE_VESSEL_APP_LD_LIBRARY_PATH". Please note that "PRESSURE_VESSEL_APP_LD_LIBRARY_PATH" will also contain the system paths that are coming from `ldconfig` (added by the "run.sh" script). Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Nov 18, 2020
-
-
Ludovico de Nittis authored
scripts: Don't assume bash is at /bin/bash See merge request steamlinuxruntime!21
-
- Nov 17, 2020
-
-
Simon McVittie authored
Apparently NixOS puts it somewhere else, although it does at least concede that a path other than /usr/bin for env is doomed to failure. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 29, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
_v2-entry-point: Check whether launch_args is empty before use See merge request steamlinuxruntime!20
-
- Oct 26, 2020
-
-
Simon McVittie authored
In newer versions of bash, an empty array counts as having been set, and can be dereferenced as `"${array[@]}"` without triggering `set -u`. However, in older versions, empty arrays count as being unset, and the entry point script fails with `launch_args[@]: unbound variable`. Resolves: https://github.com/ValveSoftware/steam-runtime/issues/284 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 22, 2020
-
-
Simon McVittie authored
Apparently Wine/Proton processes often get stuck during teardown, resulting in an unwanted delay. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 21, 2020
-
-
Timothee Besset authored
-
- Oct 02, 2020
-
-
Simon McVittie authored
_v2-entry-point: pass every environment variable See merge request steam/steamlinuxruntime!18
-
- Sep 30, 2020
-
-
Ludovico de Nittis authored
When inside a Flatpak container the socket fifo FD might be opened multiple times, for example from `flatpak-spawn --host` and from `pressure-vessel-launcher`. Normally we expected `pressure-vessel-launcher` to open the FD, write the `socket=...` into the fifo file and then close the FD. But if there is at least one other process that keeps the FD open, `_start-container-in-background` will never finish waiting to read new lines in the fifo file. Because of this we just break the loop as soon as we received what we were waiting for. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
If set, use PRESSURE_VESSEL_SOCKET_DIR in preference to XDG_RUNTIME_DIR. This is useful for example when we are in a Flatpak environment where we can't relay on XDG_RUNTIME_DIR because its value might differ between inside and outside the container. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Sep 28, 2020
-
-
Ludovico de Nittis authored
Use the new `--launcher` option instead of `--batch`. In this way `pressure-vessel` will be able to lock the environment variables that should not be copied from the environment that is running `pressure-vessel-launcher`. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
Instead of manually whitelisting all the environment variables that we might need, we pass them all. Pressure-vessel then will filter out the variables that are know to be wrong in the sandbox and the ones that will be edited. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Sep 16, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 15, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 11, 2020
-
-
Simon McVittie authored
depot: prevent unbound variable error when using empty arrays See merge request steam/steamlinuxruntime!17
-
Ludovico de Nittis authored
Previously to Bash 4.4, using `${container_args[@]}` was an error if `container_args` was an empty array. With this fix we expand to the array elements only if the array is not empty. (Fixes: T23654) Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Sep 09, 2020
-
-
Simon McVittie authored
Reduce workarounds Closes #2 See merge request steam/steamlinuxruntime!16
-
- Sep 08, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-