Skip to content

Use a better default for the graphics stack

Simon McVittie requested to merge wip/better-gfx-provider-default into master

  • pv-wrap: Don't try so hard to use host graphics by default

    For historical reasons, we assume that /run/host is a relatively complete view of the host system, like it would be inside Flatpak. However, in a systemd-nspawn container, /run/host contains other things but not usually /usr or /etc.

    Previously, the default was exactly equivalent to the old PRESSURE_VESSEL_HOST_GRAPHICS=1, which in turn is equivalent to either PRESSURE_VESSEL_GRAPHICS_PROVIDER=/run/host (if we appear to be in a container) or PRESSURE_VESSEL_GRAPHICS_PROVIDER=/ (if not).

    Now, the default is basically PRESSURE_VESSEL_GRAPHICS_PROVIDER=/, to maximize the chance that if Steam games can run in the older LD_LIBRARY_PATH-based Steam Runtime, they'll also run in our containers.

    Resolves: https://github.com/ValveSoftware/steam-runtime/issues/367

  • pv-wrap: Only use /run/host for graphics if it has both usr and etc

    If we don't have at least the equivalent of flatpak run --filesystem=host-os then we are not going to get very far.

  • pv-test-ui: Update to use PRESSURE_VESSEL_GRAPHICS_PROVIDER

  • runtime: Fix regressions when graphics provider is set to empty

    This was meant to use the graphics stack from the container itself, but we don't normally test that case (having graphics drivers is considered useful if you want to run games!) so it regressed.

Merge request reports