Skip to content

pv-exports: Treat /run/gfx the same as /run/host

Simon McVittie requested to merge wip/smcv/avoid-exporting-run-gfx into main

If the /overrides hierarchy contains a symlink to /run/gfx/something, we expect it to point into the /run/gfx that we already plan to create, so there is no need to tell FlatpakExports to look for /run/gfx/something on the host system. We already had similar logic for /run/host.

While reading the log @denittis provided for !507 (merged), I noticed this, which seems wrong:

pressure-vessel-wrap[1716]: D: Exporting /run/gfx/lib/i386-linux-gnu/libGL.so.1.7.0 because /home/pi/Downloads/steam-container-runtime/depot/var/tmp-TNQQU1/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/libGL.so.1 points to it
pressure-vessel-wrap[1716]: D: Trying to export read-only: /run/gfx/lib/i386-linux-gnu/libGL.so.1.7.0
pressure-vessel-wrap[1716]: D: Unable to open path /run/gfx/lib/i386-linux-gnu/libGL.so.1.7.0 to export read-only: No such file or directory
pressure-vessel-wrap[1716]: D: Exporting /run/gfx/lib/i386-linux-gnu/libxcb-xfixes.so.0.0.0 because /home/pi/Downloads/steam-container-runtime/depot/var/tmp-TNQQU1/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/libxcb-xfixes.so.0 points to it
pressure-vessel-wrap[1716]: D: Trying to export read-only: /run/gfx/lib/i386-linux-gnu/libxcb-xfixes.so.0.0.0
pressure-vessel-wrap[1716]: D: Unable to open path /run/gfx/lib/i386-linux-gnu/libxcb-xfixes.so.0.0.0 to export read-only: No such file or directory
pressure-vessel-wrap[1716]: D: Exporting /run/gfx/lib/i386-linux-gnu/libXdmcp.so.6.0.0 because /home/pi/Downloads/steam-container-runtime/depot/var/tmp-TNQQU1/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/libXdmcp.so.6 points to it
pressure-vessel-wrap[1716]: D: Trying to export read-only: /run/gfx/lib/i386-linux-gnu/libXdmcp.so.6.0.0
pressure-vessel-wrap[1716]: D: Unable to open path /run/gfx/lib/i386-linux-gnu/libXdmcp.so.6.0.0 to export read-only: No such file or directory
pressure-vessel-wrap[1716]: D: Exporting /run/gfx/lib/i386-linux-gnu/libX11-xcb.so.1.0.0 because /home/pi/Downloads/steam-container-runtime/depot/var/tmp-TNQQU1/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/libX11-xcb.so.1 points to it
pressure-vessel-wrap[1716]: D: Trying to export read-only: /run/gfx/lib/i386-linux-gnu/libX11-xcb.so.1.0.0
pressure-vessel-wrap[1716]: D: Unable to open path /run/gfx/lib/i386-linux-gnu/libX11-xcb.so.1.0.0 to export read-only: No such file or directory
pressure-vessel-wrap[1716]: D: Exporting /run/gfx/lib/i386-linux-gnu/libXfixes.so.3.1.0 because /home/pi/Downloads/steam-container-runtime/depot/var/tmp-TNQQU1/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/libXfixes.so.3 points to it
pressure-vessel-wrap[1716]: D: Trying to export read-only: /run/gfx/lib/i386-linux-gnu/libXfixes.so.3.1.0
pressure-vessel-wrap[1716]: D: Unable to open path /run/gfx/lib/i386-linux-gnu/libXfixes.so.3.1.0 to export read-only: No such file or directory

It's harmless in practice, because /run/gfx doesn't exist on the host in practice anyway - but it's also silly and noisy.

Merge request reports