Simon McVittie

@DistantThunder You are not experiencing the same bug as the original reporter of this issue. The key thing in your log is: ``` bwrap: Can't mkdir /usr/lib32/gconv: Read-only file system...

The original issue reported here is *partially* fixed in pressure-vessel versions >= 0.20210105.0. `/tmp` being a symlink should now be OK, although I would still recommend using bind-mounts instead of...

> I noticed in the system information linked above that the i386 vulkan part includes the shared objects of 64 bit and x86_64 includes the 32 bit version of vulkan...

Please could someone with the right permissions retitle this to `PRESSURE_VESSEL_SHARE_HOME=0 not compatible with cloud saves yet` to flag it as a known-missing feature that affects multiple games?

More specifically, the problem seems to be that if there's an abstract socket `@/tmp/.X11-unix/X99` on the host system, libX11 inside the container will prefer to connect to that, whereas what...

Sorry, that workaround can work for Flatpak but not for the Steam container runtime. Because your graphics drivers depend on libX11/libxcb (in practice `libGLX.so.0` does), we have to borrow the...

https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/merge_requests/484

If you want to try out a proposed solution to this and you're comfortable with using prerelease software, you can replace `SteamLinuxRuntime_soldier/pressure-vessel` with the result of unpacking this: https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/jobs/99708/artifacts/raw/_build/production/pressure-vessel-bin.tar.gz Use...

> Out of curiosity, may I ask why is this not done originally? The container setup code is borrowed from Flatpak, which is known to work on lots of systems,...

Today's `SteamLinuxRuntime_soldier` and `SteamLinuxRuntime_sniper` betas contain the same solution to this as the prerelease described in https://github.com/ValveSoftware/steam-runtime/issues/524#issuecomment-1209638215. This change will land in the stable versions of soldier and sniper in...