protonscr

[SteamRT3] Storage drive is reported as "/run/host/usr"

steamopen Steam clientruntime
ValveSoftware/steam-for-linux#13049 · opened 2026-03-29 by L1Q · updated 2026-04-08 · 3 comments · github
LL1Q 2026-03-29 github

Your system information

  • Steam client version (build number or date): 1774577504
  • Distribution: Arch
  • Opted into Steam client beta?: Yes
  • Have you checked for system updates?: Yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: AMD
  • Steam directory is /home/l1q/.local/share/Steam/
  • game install directory is the default as well /home/l1q/.local/share/Steam/steamapps/common/

Please describe your issue in as much detail as possible:

Normal beta version reports my root drive as "Local Drive (/)", SteamRT3 calls it "/run/host/usr" everywhere. The actual install paths, "browse local files" and similar actions work as usual.

Steps for reproducing this issue:

  1. Use SteamRT3
  2. View anything related to storage: start installing a game, installed games' properties -> Installed Files, Settings -> Storage
  3. Observe something like "Local Drive (/)" being reported as "/run/host/usr", slightly different drive usage reported.

Screenshots

Expected:

Normal beta game install dialog Image
Normal beta game installed files Image
Normal beta Storage Settings Image

SteamRT3:

SteamRT3 game install dialog Image
SteamRT3 game installed files Image
SteamRT3 Storage Settings Image
LL1Q 2026-04-02 github

updating my post with steam logs, I'm observing mentions of "/run/host/usr" paths next to pressure-vessel related erros:

steam-runtime-launcher-service[331499]: I: Running spawn command lsb_release
pressure-vessel-wrap[332000]: W: "run/host/usr/lib/ld-linux-x86-64.so.2" is unlikely to appear in "/run/host"
pressure-vessel-wrap[332000]: W: "run/host/usr/lib/ld-linux-x86-64.so.2" is unlikely to appear in "/run/host"
steam-runtime-launcher-service[331499]: I: Running spawn command lspci
steam-runtime-launcher-service[331499]: I: Running spawn command lsb_release
pressure-vessel-wrap[332000]: W: "run/host/usr/lib32/ld-linux.so.2" is unlikely to appear in "/run/host"
pressure-vessel-wrap[332000]: W: "run/host/usr/lib32/ld-linux.so.2" is unlikely to appear in "/run/host"
bwrap: execvp /usr/lib/pressure-vessel/from-host/libexec/steam-runtime-tools-0/pv-adverb: Too many levels of symbolic links
[331707:331707:0402/142238.243084:ERROR:atom_cache.cc(229)] Add _NET_WM_STATE_KEEP_ABOVE to kAtomsToCache
pressure-vessel-wrap[332143]: W: "run/host/usr/lib/ld-linux-x86-64.so.2" is unlikely to appear in "/run/host"
pressure-vessel-wrap[332143]: W: "run/host/usr/lib/ld-linux-x86-64.so.2" is unlikely to appear in "/run/host"
pressure-vessel-wrap[332143]: W: "run/host/usr/lib32/ld-linux.so.2" is unlikely to appear in "/run/host"
pressure-vessel-wrap[332143]: W: "run/host/usr/lib32/ld-linux.so.2" is unlikely to appear in "/run/host"
bwrap: execvp /usr/lib/pressure-vessel/from-host/libexec/steam-runtime-tools-0/pv-adverb: Too many levels of symbolic links
Ssmcv 2026-04-08 github

I'm observing mentions of "/run/host/usr" paths next to pressure-vessel related erros

These are unrelated to the original issue you reported: they're more closely related to #13036 and #13006.

Ssmcv 2026-04-08 github

The mis-labelling is because the Steam client is now running inside a container, which has various parts of the real machine's filesystem mounted at paths inside the container. When it chooses a default name for a Steam library, it tries to use the mount point for the filesystem containing that directory, as an approximate Linux equivalent of Windows drive letters; but because different parts of the same filesystem are mounted in several places inside the container, it gets confused, and chooses the first one that appears in the mount table (or possibly the last one), which in your case happens to be the real machine's /usr mounted on the container's /run/host/usr.

Nothing extracted yet.