- Jan 27, 2022
-
-
Simon McVittie authored
In situations where Steam is providing the whole UI, such as Steam Deck and Big Picture mode, we might want to prioritize steam.pipe higher than x-d-p, so that Steam has the opportunity to choose what the UX will be (launching an external browser, vs. showing the web page in-process using CEF and steamwebhelper). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
In cases where we tried both steam.pipe and xdg-desktop-portal, this lets us show both their errors, instead of only the most recent. 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>
-
- Jan 13, 2022
-
-
Simon McVittie authored
These are used by the NVIDIA proprietary driver for integration with non-X11 display technologies such as Wayland and gbm. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Dec 03, 2021
-
-
Simon McVittie authored
This gives us a better version number, from the Vulkan driverInfo. It also lets us see the driver name and the machine-readable VkDriverId. Resolves: #79 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 20, 2021
-
-
Ludovico de Nittis authored
Steam is x86-specific, but the majority of steam-runtime-tools is architecture-agnostic. Adding one arbitrary non-x86 architecture gives us a way to evaluate how much work would be required if full support for some other architecture is needed in future. Using aarch64 seems the easiest non-x86 to test with real hardware, since the Raspberry Pi 4 is widely available. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Sep 30, 2021
-
-
Ludovico de Nittis authored
When getting modules from a specific path, if there was an absolute symlink, we could have ended up enumerating the modules from outside the expected sysroot. We can prevent that by using `_srt_resolve_in_sysroot`. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Sep 29, 2021
-
-
Ludovico de Nittis authored
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Sep 23, 2021
-
-
Simon McVittie authored
This drops the dependency on json-glib from check-requirements. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This lets us link simpler modules like architecture.c and cpu-feature.c into a CLI program like steam-runtime-check-requirements without pulling in json-glib. graphics.c, locale.c and xdg-portal.c continue to contain their own JSON report parsing code, because those translation units need to parse helper programs' JSON output *anyway*. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 05, 2021
-
-
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>
-
- Jun 28, 2021
-
-
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>
-
- May 27, 2021
-
-
Simon McVittie authored
This is helpful if we're stacking the scout runtime onto the soldier runtime: both pinned_libs_* and overrides are relevant there. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 27, 2021
-
-
Ludovico de Nittis authored
If we are in a Flatpak container it can be useful to have the Flatpak version in the system report. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Apr 22, 2021
-
-
Ludovico de Nittis authored
When loading VDPAU modules we rely on $PLATFORM, trying to support all its known possible expansions. However there is always the possibility that we are currently missing some of them or that new ones will be added in the future. For this reason we try to detect the expansion of $PLATFORM, and $LIB, and print its value in the report. In this way it will be easier to notice unusual and/or new expansions. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Mar 31, 2021
-
-
When inside a Steam Runtime container we currently make `xdg-open` points to the `flatpak-xdg-utils` implementation that relies on `xdg-desktop-portal`. But if an user doesn't have a working `xdg-desktop-portal` it will fail. Additionally the `steam://` URLs might end up opening another instance of the Steam client, even if one instance was already running. This can happen if more than one version are installed, e.g. the Steam client from the distro repositories and the Flatpak version. With this alternative implementation we try a more clever approach that should workaround the `xdg-open` shortcomings that we experienced in our Steam related use cases. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com> [smcv: Install all /usr/bin/steam-runtime-* executables] Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Mar 30, 2021
-
-
Ludovico de Nittis authored
This stub steam executable tries to directly pass the given commands, e.g. "steam://nav/downloads ", to the running Steam client, if any. This helps games that tries to run "steam ${command}" because when we are in a LD_LIBRARY_PATH runtime, "steam" might not be pointing to the same version that is currently running. Or if we are in a container, there is no "steam" executable in the PATH at all. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Mar 23, 2021
-
-
Simon McVittie authored
JSON strings must be valid Unicode, so use the lossy transformation in g_utf8_make_valid() to replace non-UTF-8 (if found) with U+FFFD REPLACEMENT CHARACTER. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Feb 22, 2021
-
-
Ludovico de Nittis authored
With the additional "issues" entry in the s-r-s-i report we can now flag the ICDs/layers as being duplicated or also unsupported. This makes it easier to spot misconfigured systems or also regressions about how we import ICDs/layers inside the container. Fixes: T26156 Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jan 28, 2021
-
-
Ludovico de Nittis authored
Now that check-vulkan prints detailed information about every physical and virtual Vulkan GPU, we can start to provide this info in s-r-s-i too. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jan 25, 2021
-
-
Simon McVittie authored
A single line with escaped newlines is unnecessarily hard to read. This repurposes code that we already had for printing a udev uevent pseudo-file in this way. We retain the ability to parse old s-r-s-i output in which the diagnostic messages were a string: the intended meaning is fairly obvious. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
The reference is now the man page. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Nov 18, 2020
-
-
Simon McVittie authored
On operating systems with unusual path layouts, such as Exherbo and NixOS, the de facto standard path for the runtime linker is not necessarily present for all architectures. (Of course, if the x86_64 runtime linker is not present, we won't normally be able to run steam-runtime-system-info either, but at least users of such operating systems can compile it from source code if they need to provide diagnostics.) Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Nov 17, 2020
-
-
Ludovico de Nittis authored
Similarly to what we already have for ICDs, we are now able to parse the Vulkan layers JSON files and add this information in the report. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
This function allow us to avoid some repetitive codes when constructing a new JSON file. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Nov 10, 2020
-
-
Simon McVittie authored
These are what we really want for SDL and Wine: they're broadly equivalent to the udev ID_INPUT_FOO properties, and identify which devices are desired at a high level. Also add test coverage for the device-type-guessing heuristic. Thanks to various people in Collabora, Codeweavers and #debian-uk for providing `sudo evemu-describe` output for their devices. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
These are a useful input for guessing what an input device is. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This is the official way to determine what an input device is, at the kernel level. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
The name is to leave space for "type flags" (joystick, etc.) later. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Wine/Proton needs these for some of its HID functionality. 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
This is the same approach used by SDL. It doesn't work well in most containers. To facilitate testing this, change sysroot/run-in-sysroot.py so that it doesn't share /run with the host, and signals "we're in a container" by creating /run/host. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This includes: * a public interface implemented by input device monitors * a public interface to be implemented by the input devices they signal * a mock implementation for unit-testing * a unit test for the API * a simple implementation in terms of inotify on /dev * a monitor that can print input devices in JSON format on stdout, and optionally monitor them Implementations in terms of udev, SDL, or a portal service are not yet included. Details of the devices, beyond their paths in /dev and /sys, are also not included. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 26, 2020
-
-
Ludovico de Nittis authored
Print in the steam-runtime-system-info report the information we know about the xdg-portal support. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Oct 22, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-