- Sep 25, 2019
-
-
Simon McVittie authored
Until now we've been conflating these two, but Timothee Besset recently clarified their status for me. ~/.steam/steam is maintained by bin_steam.sh, aka /usr/bin/steam, in which it is referred to as STEAMDATALINK. It is the data directory containing user data (cloud-synced configuration and saves), the download cache, and the default Steam Library directory. ~/.steam/root is maintained by steam.sh, in which it is referred to as STEAMROOTLINK. It is the installation directory, containing Steam executables and libraries. As a result, they are normally the same, but can differ, in particular in two situations: * When testing a new Steam client build by running client/steam.sh, client/ gets used as the installation directory, in conjunction with the existing data directory pointed to by ~/.steam/steam. This avoids having to re-login or re-download your library of games for the new test installation. * When Debian bug #916303 was present during the initial Steam installation, the Steam client was unpacked into ~/.steam, resulting in creation of ~/.steam/steam as a real directory that cannot be replaced with a symbolic link. We effectively ended up using ~/.steam as the installation path, but with ~/.steam/steam as the data path. (The Debian steam package has since been fixed, but we cannot easily disentangle existing installations.) Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 24, 2019
-
-
Simon McVittie authored
This is necessary for pressure-vessel containers to support Vulkan: to be able to make the Vulkan ICDs available in the container, we have to be able to find them, bind-mount them into a suitable location, and provide corresponding ICD JSON metadata to the contained game. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 11, 2019
-
-
Simon McVittie authored
pressure-vessel will use these when it generates any missing locales. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 10, 2019
-
-
Simon McVittie authored
Rather than dumping this to Steam's stderr, it's more useful if we gather it up and make it available alongside all the other diagnostic information. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 09, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Aug 27, 2019
-
-
Simon McVittie authored
Some Steam games assume that the en_US.UTF-8 locale is available, and it's reasonably likely that others assume that the C.UTF-8 locale is available, or that the locale environment variables are set to usable values. Having checks for locale properties will also help us when experimenting with containers: we can check whether the locale that was set outside the container is available inside the container. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Aug 21, 2019
-
-
Jeremy Whiting authored
Moved srt_check_graphics to _srt_check_graphics and made it internal. Call _srt_check_graphics from srt_system_info_check_graphics after checking if we have a cached result first. Changed graphics test to use srt_system_info to do the check_graphics tests. Pass helpers_path to _srt_check_graphics and prepend path if set. Add srt_sytem_info_check_all_graphics. In srt_system_info_check_all_graphics try each of the 4 combinations of window system and renderer and report back a GList of results. Also added to bin/steam-system-info.c using srt_system_info_check_all_graphics and outputting all found information in json format. Also added use of LD_PRELOAD environment variable. Also changed call to g_spawn_sync to search PATH so it can find -wflinfo binaries.
-
- Aug 15, 2019
-
-
Now we should be able to detect when the Steam Runtime environmental setup has been modified by the distro or user. Co-authored-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Aug 12, 2019
-
-
Simon McVittie authored
We can at least print "unknown-expectations" in the summary of issues. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Aug 06, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Otherwise, if we process an architecture we can run before an architecture we can't, we'll try to free the old list twice. This happens on i386 autobuilders that can't run x86_64 executables. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This has become less an example and more a command-line driver for the library, so rename it accordingly. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-