- Jul 20, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Adjust LD_PRELOAD and LD_AUDIT to prevent ELF warnings See merge request !333
-
Simon McVittie authored
Optionally run each pressure-vessel game in a systemd scope See merge request !328
-
Simon McVittie authored
This neatly separates the processes for the game (which can be numerous, for example for Proton games that need to run wineserver and winedevice.exe) from the processes for Steam. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Taken from Flatpak 1.11.2. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
When a game is launched with the Steam Overlay feature enabled (it's on by default), we end up with an LD_PRELOAD that contains `gameoverlayrenderer.so` two times, one for 32-bit and the other for 64-bit processes. However this leads to a warning that is harmless but scary for users and developers unaware of that: `ERROR: ld.so: object '/home/me/.local/share/steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.` And every 64-bit process prints something similar about the ELFCLASS32. By creating a temporary directory and using the dynamic linker token expansion `$PLATFORM` we can let a process preload only the `gameoverlayrenderer.so` for the right ABI. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Simon McVittie authored
pressure-vessel: Remove the concept of "locking" environment variables See merge request !329
-
Ludovico de Nittis authored
runtime: Look for NVIDIA driver data in /usr/share/nvidia first Closes #73 See merge request !335
-
Simon McVittie authored
This was only necessary because we were reusing a single container across multiple entry-point invocations, and expecting "most" arbitrary environment variables from each new invocation to be taken into account for commands running in the container, which meant that we needed to keep track of which environment variables had to be exceptions to that rule for technical reasons. Now that we're no longer injecting multiple commands into the same container like that, we don't need this complexity. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
If we have libGLX_nvidia.so.0 for *any* architecture - even if we are msising some instances - then we still want to share /usr/share/nvidia with the container. Because we always use libGLX_nvidia.so.0 from the graphics stack provider and do not have a concept of whether it is older or newer, and we do not expect our runtime to have a copy of libGLX_nvidia.so.0, we do not need to worry about giving the runtime's library an incompatible version of the data files from the provider. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
The NVIDIA driver hard-codes /usr/share/nvidia even if it is installed in /opt or something, so instead of deriving ${prefix} from the library path and then checking for ${prefix}/share/nvidia followed by /usr/share/nvidia as a fallback, we do the opposite: check for /usr/share/nvidia first, followed by ${prefix}/share/nvidia as a fallback. Signed-off-by:
Simon McVittie <smcv@collabora.com> Resolves: #73 (T29292)
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 19, 2021
-
-
Simon McVittie authored
runtime: try to bind /etc/nvidia and /usr/share/nvidia Closes #73 See merge request !334
-
- Jul 14, 2021
-
-
Ludovico de Nittis authored
If we have libGLX_nvidia.so.0 from the provider, we should also bind `/etc/nvidia` and `/usr/share/nvidia` because they usually contain the application profiles. http://us.download.nvidia.com/XFree86/Linux-x86_64/470.42.01/README/profiles.html#ApplicationProf9ccbe Fixes: #73 Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jul 05, 2021
-
-
Simon McVittie authored
Add licensing information in REUSE format See merge request !332
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 02, 2021
-
-
Simon McVittie authored
tests: Make sure artifacts directory is shared with container See merge request !331
-
Simon McVittie authored
If the artifacts directory is a symlink (or has a symlink in one of its parents) then we need to make sure that both the symlink and its target get shared with the container. We have code for that; use it. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 01, 2021
-
-
Simon McVittie authored
We exercise scout via the .deb packaging, there's little point in doing a redundant set of builds. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 30, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
In particular this lets us gather detached debug symbols from the generated -dbgsym packages. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Add executable that identifies the ABI of libraries See merge request !326
-
- Jun 28, 2021
-
-
Ludovico de Nittis authored
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
This is useful when we want to differentiate the available libraries based on the architecture they are compiled against. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jun 24, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
wrap: Execute nvidia-modprobe with the -c=0 option See merge request !327
-
Ludovico de Nittis authored
It has been reported that `nvidia-modprobe -u` might not be enough to enable the Nvidia Vulkan ray-tracing: https://github.com/HansKristian-Work/vkd3d-proton/issues/711 Apparently `nvidia-modprobe` needs to be called with the option `-c=0` such that it will create the `/dev/nvidia-uvm` device file if it doesn't already exist. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jun 17, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Document the Steam compatibility tool interface See merge request !324
-
Ludovico de Nittis authored
Fix interop with older Upstart- and sysvinit-based OSs See merge request !325
-
Simon McVittie authored
This can be the case on older sysvinit- or Upstart-based Debian-derived distributions, such as Ubuntu 14.04 (with the default Upstart init system) and Debian 9 (with the non-default sysvinit init system). Under systemd or the versions of sysvinit in Debian >= 10, /dev/shm is a real tmpfs and /run/shm is a symlink to /dev/shm. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-