Same issue, also on Gentoo (but with CachyOS kernel if that matters), also on the SteamRT3 beta. Saw the steam update popup, but it will not launch.
Edit: removing myself from the steam beta (by moving .steam/steam/package/beta out of that dir to my home dir) allowed steam to launch as normal.
steam.sh[5795]: Starting SteamRT3 Steam
CProcessEnvironmentManager is ready, 5 preallocated environment variables.
RunCommand: /home/nick/.local/share/Steam/steamrt64/pv-runtime/steam-runtime-steamrt/bin/steam-runtime-check-requirements 2>&1
[2026-09-09 22:28:46] Startup - updater built Sep 9 2026 21:03:04
[2026-09-09 22:28:46] Startup - Steam Client launched with: '/home/nick/.local/share/Steam/steamrt64/steam' '-srt-logger-opened'
[2026-09-09 22:28:46] Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
09/09 22:28:46 minidumps folder is set to /tmp/dumps
09/09 22:28:46 Init: Installing breakpad exception handler for appid(steam)/version(1788989629)/tid(5808)
CProcessEnvironmentManager is ready, 5 preallocated environment variables.
[2026-09-09 22:28:46] Process started with command-line: '/home/nick/.local/share/Steam/steamrt64/steam' '-child-update-ui' '-child-update-ui-socket' '9' '-srt-logger-opened'
[2026-09-09 22:28:46] Loading cached metrics from disk (/home/nick/.local/share/Steam/package/steam_client_metrics.bin)
09/09 22:28:46 minidumps folder is set to /tmp/dumps
[2026-09-09 22:28:46] Using the following download hosts for Public, Realm steamglobal
[2026-09-09 22:28:46] 1. https://client-update.fastly.steamstatic.com, /, Realm 'steamglobal', weight was 900, source = 'update_hosts_cached.vdf'
[2026-09-09 22:28:46] 2. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 400, source = 'update_hosts_cached.vdf'
[2026-09-09 22:28:46] 3. https://client-update.steamstatic.com, /, Realm 'steamglobal', weight was 1, source = 'baked in'
[2026-09-09 22:28:46] Verifying installation...
[2026-09-09 22:28:46] Verifying file sizes only
[2026-09-09 22:28:46] Using update UI: xwin
09/09 22:28:46 Init: Installing breakpad exception handler for appid(steam)/version(0)/tid(5815)
[2026-09-09 22:28:46] Create window
[2026-09-09 22:28:46] Verification complete
UpdateUI: skip show logo
Updating symlink: /home/nick/.steam/bin32 -> /home/nick/.local/share/Steam/steamrt32
Updating symlink: /home/nick/.steam/bin64 -> /home/nick/.local/share/Steam/steamrt64
Updating symlink: /home/nick/.steam/sdk32 -> /home/nick/.local/share/Steam/linux32
Updating symlink: /home/nick/.steam/sdk64 -> /home/nick/.local/share/Steam/linux64
Updating symlink: /home/nick/.steam/root -> /home/nick/.local/share/Steam/
Updating symlink: /home/nick/.steam/steam -> /home/nick/.local/share/Steam/
srt-logger: disabled, already open
ReexecToLauncher: opted into beta
ReexecToLauncher: opted into steamrt3 client
ReexecToLauncher: proceeding in current environment
[2026-09-09 22:28:46] Shutdown
[2026-09-09 22:28:46] Set percent complete: 0
[2026-09-09 22:28:46] Set percent complete: -1
[2026-09-09 22:28:46] Set status message: Verifying installation...
[2026-09-09 22:28:46] ProcessNextMessage: socket disconnected
[2026-09-09 22:28:46] No more messages are expected - exiting
ReexecSteamLinux: received re-exec request with code: 67 steamrt: 0
WARNING: SDL_VIDEODRIVER='wayland,x11,windows' does not allow fallback. Appending 'x11,windows'
ReexecSteamLinux: re-launching steam in SteamRT runtime
pressure-vessel-wrap[5842]: E: This program should not be run in the Steam Runtime. Use pressure-vessel-unruntime instead.
ReexecSteamLinux: exitingsteam.sh[5795]: Starting SteamRT3 Steam
CProcessEnvironmentManager is ready, 5 preallocated environment variables.
RunCommand: /home/nick/.local/share/Steam/steamrt64/pv-runtime/steam-runtime-steamrt/bin/steam-runtime-check-requirements 2>&1
[2026-09-09 22:28:46] Startup - updater built Sep 9 2026 21:03:04
[2026-09-09 22:28:46] Startup - Steam Client launched with: '/home/nick/.local/share/Steam/steamrt64/steam' '-srt-logger-opened'
[2026-09-09 22:28:46] Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
09/09 22:28:46 minidumps folder is set to /tmp/dumps
09/09 22:28:46 Init: Installing breakpad exception handler for appid(steam)/version(1788989629)/tid(5808)
CProcessEnvironmentManager is ready, 5 preallocated environment variables.
[2026-09-09 22:28:46] Process started with command-line: '/home/nick/.local/share/Steam/steamrt64/steam' '-child-update-ui' '-child-update-ui-socket' '9' '-srt-logger-opened'
[2026-09-09 22:28:46] Loading cached metrics from disk (/home/nick/.local/share/Steam/package/steam_client_metrics.bin)
09/09 22:28:46 minidumps folder is set to /tmp/dumps
[2026-09-09 22:28:46] Using the following download hosts for Public, Realm steamglobal
[2026-09-09 22:28:46] 1. https://client-update.fastly.steamstatic.com, /, Realm 'steamglobal', weight was 900, source = 'update_hosts_cached.vdf'
[2026-09-09 22:28:46] 2. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 400, source = 'update_hosts_cached.vdf'
[2026-09-09 22:28:46] 3. https://client-update.steamstatic.com, /, Realm 'steamglobal', weight was 1, source = 'baked in'
[2026-09-09 22:28:46] Verifying installation...
[2026-09-09 22:28:46] Verifying file sizes only
[2026-09-09 22:28:46] Using update UI: xwin
09/09 22:28:46 Init: Installing breakpad exception handler for appid(steam)/version(0)/tid(5815)
[2026-09-09 22:28:46] Create window
[2026-09-09 22:28:46] Verification complete
UpdateUI: skip show logo
Updating symlink: /home/nick/.steam/bin32 -> /home/nick/.local/share/Steam/steamrt32
Updating symlink: /home/nick/.steam/bin64 -> /home/nick/.local/share/Steam/steamrt64
Updating symlink: /home/nick/.steam/sdk32 -> /home/nick/.local/share/Steam/linux32
Updating symlink: /home/nick/.steam/sdk64 -> /home/nick/.local/share/Steam/linux64
Updating symlink: /home/nick/.steam/root -> /home/nick/.local/share/Steam/
Updating symlink: /home/nick/.steam/steam -> /home/nick/.local/share/Steam/
srt-logger: disabled, already open
ReexecToLauncher: opted into beta
ReexecToLauncher: opted into steamrt3 client
ReexecToLauncher: proceeding in current environment
[2026-09-09 22:28:46] Shutdown
[2026-09-09 22:28:46] Set percent complete: 0
[2026-09-09 22:28:46] Set percent complete: -1
[2026-09-09 22:28:46] Set status message: Verifying installation...
[2026-09-09 22:28:46] ProcessNextMessage: socket disconnected
[2026-09-09 22:28:46] No more messages are expected - exiting
ReexecSteamLinux: received re-exec request with code: 67 steamrt: 0
WARNING: SDL_VIDEODRIVER='wayland,x11,windows' does not allow fallback. Appending 'x11,windows'
ReexecSteamLinux: re-launching steam in SteamRT runtime
pressure-vessel-wrap[5842]: E: This program should not be run in the Steam Runtime. Use pressure-vessel-unruntime instead.
ReexecSteamLinux: exiting
Same issue. Can't launch Steam at all for me, but given I have no 32-bit libraries I kind of asked for it 😆
Anyone in the same position can just launch it with this:
env -u PRESSURE_VESSEL_ENTRY_POINT -u PRESSURE_VESSEL_CONTAINER_NAME ~/.local/share/Steam/steamrt64/steam
Thanks for the issue report.
@RLB2310 does it also work if you launch the binary directly, .e.g.
~/.local/share/Steam/steamrt64/steam
Or does it only work when you explicitly unset the env vars:
env -u PRESSURE_VESSEL_ENTRY_POINT -u PRESSURE_VESSEL_CONTAINER_NAME ~/.local/share/Steam/steamrt64/steam
~/.local/share/Steam/steamrt64/steam
Hi @lostgoat. Running the binary directly does work for me yes. However I believe it initially did not, as I did attempt to try it (which lead to unsetting the pressure-vessel env vars).
Here is logs from when I attempted with PV:
~/.local/share/Steam/steamrt64/pv-runtime/steam-runtime-steamrt/pressure-vessel/bin/pressure-vessel-unruntime ~/.local/share/Steam/steamrt64/steam 2 err 23s 14:55:34
pv-adverb[7052]: W: Unable to identify uniquely identifying libdl tokens (Unable to determine ${LIB} for i386-linux-gnu: Failed to execute child process “/home/rylan/.local/share/Steam/steamrt64/pv-runtime/steam-runtime-steamrt/pressure-vessel/libexec/steam-runtime-tools-0/i386-linux-gnu-detect-lib” (No such file or directory); Unable to determine ${PLATFORM} for i386-linux-gnu: Failed to execute child process “/home/rylan/.local/share/Steam/steamrt64/pv-runtime/steam-runtime-steamrt/pressure-vessel/libexec/steam-runtime-tools-0/i386-linux-gnu-detect-platform” (No such file or directory))
CProcessEnvironmentManager is ready, 5 preallocated environment variables.
Updating symlink: /home/rylan/.steam/bin32 -> /home/rylan/.local/share/Steam/steamrt32
Updating symlink: /home/rylan/.steam/bin64 -> /home/rylan/.local/share/Steam/steamrt64
Updating symlink: /home/rylan/.steam/sdk32 -> /home/rylan/.local/share/Steam/linux32
Updating symlink: /home/rylan/.steam/sdk64 -> /home/rylan/.local/share/Steam/linux64
Updating symlink: /home/rylan/.steam/root -> /home/rylan/.local/share/Steam/
Updating symlink: /home/rylan/.steam/steam -> /home/rylan/.local/share/Steam/
RunCommand: /home/rylan/.local/share/Steam/steamrt64/pv-runtime/steam-runtime-steamrt/bin/steam-runtime-check-requirements 2>&1
[2026-09-10 14:55:39] Startup - updater built Sep 9 2026 21:03:04
[2026-09-10 14:55:39] Startup - Steam Client launched with: '/home/rylan/.local/share/Steam/steamrt64/steam'
[2026-09-10 14:55:39] Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
09/10 14:55:39 minidumps folder is set to /tmp/dumps
09/10 14:55:39 Init: Installing breakpad exception handler for appid(steam)/version(1788989629)/tid(7057)
CProcessEnvironmentManager is ready, 5 preallocated environment variables.
[2026-09-10 14:55:39] Loading cached metrics from disk (/home/rylan/.local/share/Steam/package/steam_client_metrics.bin)
[2026-09-10 14:55:39] Using the following download hosts for Public, Realm steamglobal
[2026-09-10 14:55:39] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 400, source = 'update_hosts_cached.vdf'
[2026-09-10 14:55:39] 2. https://client-update.fastly.steamstatic.com, /, Realm 'steamglobal', weight was 900, source = 'update_hosts_cached.vdf'
[2026-09-10 14:55:39] 3. https://client-update.steamstatic.com, /, Realm 'steamglobal', weight was 1, source = 'baked in'
[2026-09-10 14:55:39] Verifying installation...
[2026-09-10 14:55:39] Verifying file sizes only
[2026-09-10 14:55:39] Process started with command-line: '/home/rylan/.local/share/Steam/steamrt64/steam' '-child-update-ui' '-child-update-ui-socket' '9'
09/10 14:55:39 minidumps folder is set to /tmp/dumps
[2026-09-10 14:55:39] Using update UI: xwin
09/10 14:55:39 Init: Installing breakpad exception handler for appid(steam)/version(0)/tid(7063)
[2026-09-10 14:55:39] Create window
[2026-09-10 14:55:39] Set percent complete: 0
[2026-09-10 14:55:39] Set percent complete: -1
[2026-09-10 14:55:39] Set status message: Verifying installation...
[2026-09-10 14:55:39] Verification complete
UpdateUI: skip show logo
ReexecToLauncher: opted into beta
ReexecToLauncher: opted into steamrt3 client
ReexecToLauncher: proceeding in current environment
[2026-09-10 14:55:39] Shutdown
[2026-09-10 14:55:39] ProcessNextMessage: socket disconnected
[2026-09-10 14:55:39] No more messages are expected - exiting
ReexecSteamLinux: received re-exec request with code: 67 steamrt: 0
ReexecSteamLinux: re-launching steam in SteamRT runtime
ERROR: pv-run.sh: Cannot be run inside a pressure-vessel container
ReexecSteamLinux: exiting `
@RLB2310 thanks for confirming.
Can't launch Steam at all for me, but given I have no 32-bit libraries I kind of asked for it
Steam still requires both 64-bit and 32-bit libraries (at least glibc and Mesa), even with the experimental 64-bit/steamrt3c client.
Steam still requires both 64-bit and 32-bit libraries (at least glibc and Mesa), even with the experimental 64-bit/steamrt3c client.
I am aware it's not officially supported, yeah. But I believe this issue thread is not related to that, as it has only occurred between the last update.
I have another thread open regarding that specifically and how it can be traversed (unofficially of course) open at #13015
Here is my system without 32-bit (as well as no 32-bit Mesa) support
Where did you get Steam packaging for Gentoo from? Is it https://github.com/anyc/steam-overlay or something else?
What is the text of the steam script in your PATH? I suspect that it's setting environment variables that are meant to only be set internally by Steam, like STEAM_RUNTIME, and this is what's causing the error message This program should not be run in the Steam Runtime.
~/.local/share/Steam/steamrt64/pv-runtime/steam-runtime-steamrt/pressure-vessel/bin/pressure-vessel-unruntime ~/.local/share/Steam/steamrt64/steam
This is not a command that is meant to work: parts of the Steam Client need to run outside the container (and they will start a container internally to run the parts of the Steam Client that can/should be containerized). This is why you got the error message ERROR: pv-run.sh: Cannot be run inside a pressure-vessel container.
PRESSURE_VESSEL_ENTRY_POINT,PRESSURE_VESSEL_CONTAINER_NAME
These environment variables aren't used by pressure-vessel and shouldn't have any effect, unless the Steam Client uses them internally for some reason.
Steam still requires both 64-bit and 32-bit libraries (at least glibc and Mesa), even with the experimental 64-bit/steamrt3c client.
I am aware it's not officially supported, yeah.
This is relevant because if you're using workarounds to achieve something that isn't supported, then it's entirely possible for those workarounds to interfere with an updated Steam Client.
Where did you get Steam packaging for Gentoo from? Is it https://github.com/anyc/steam-overlay or something else?
Yep exactly, Gentoo Steam overlay.
What is the text of the
steamscript in yourPATH? I suspect that it's setting environment variables that are meant to only be set internally by Steam, likeSTEAM_RUNTIME, and this is what's causing the error messageThis program should not be run in the Steam Runtime.
Running in my terminal without a launch wrapper, Steam is located at /usr/bin/steam and has the following contents:
# Set a default STEAM_RUNTIME value.
: ${STEAM_RUNTIME:=1}
export STEAM_RUNTIME
# Gentoo's lsb-release doesn't set this.
export DISTRIB_RELEASE="1.0.0.85-r3"
# Add paths to occasionally needed libraries not found in /usr/lib.
export LD_LIBRARY_PATH+="${LD_LIBRARY_PATH+:}/usr/\${LIB}/debiancompat:/usr/\${LIB}/fltk"
# Preload the extest library when running in a Wayland session.
[[ -f "/usr/lib/libextest.so" && ${XDG_SESSION_TYPE} == wayland ]] &&
export LD_PRELOAD+="${LD_PRELOAD+:}/usr/lib/libextest.so"
# Preload libstdc++ on default-libcxx systems to avoid crashes. Loading the
# 64-bit library prevents Steam from working at all, so only load the 32-bit
# multlib library. Pure 32-bit systems are untested and may not work.
if grep -Fxqe --stdlib=libc++ /etc/clang/gentoo-runtimes.cfg 2>/dev/null; then
IFS=:
for GCC_LIB_DIR in $(gcc-config -L 2>/dev/null); do
[[ ${GCC_LIB_DIR} == */32 ]] || continue
export LD_PRELOAD+="${LD_PRELOAD+:}${GCC_LIB_DIR}/libstdc++.so"
done
unset IFS GCC_LIB_DIR
fi
# Steam renames LD_LIBRARY_PATH to SYSTEM_LD_LIBRARY_PATH and it then becomes
# ineffective against games. We unfortunately therefore have to force the value
# through via STEAM_RUNTIME_LIBRARY_PATH instead.
export STEAM_RUNTIME_LIBRARY_PATH="${LD_LIBRARY_PATH}"
. "${0%/*}"/../lib/steam/bin_steam.sh
~/.local/share/Steam/steamrt64/pv-runtime/steam-runtime-steamrt/pressure-vessel/bin/pressure-vessel-unruntime ~/.local/share/Steam/steamrt64/steamThis is not a command that is meant to work: parts of the Steam Client need to run outside the container (and they will start a container internally to run the parts of the Steam Client that can/should be containerized). This is why you got the error message
ERROR: pv-run.sh: Cannot be run inside a pressure-vessel container.
Ah I see now. Not really knowledgeable when it comes to Pressure-vessel or bubblewrap, thanks for clarifying.
PRESSURE_VESSEL_ENTRY_POINT,PRESSURE_VESSEL_CONTAINER_NAMEThese environment variables aren't used by pressure-vessel and shouldn't have any effect, unless the Steam Client uses them internally for some reason.
Interesting. I might've been wrong about it being the fix. Possibly just using the binary directly @ ~/.local/share/Steam/steamrt64/steam like @lostgoat suggested should be enough for whatever the last update changed then. Something on my end must've gone wrong when I initially tried it. Then again my setup isn't really representative of a system Steam should be run on.
I still only had the launch issue today after the latest update, but replacing my Steam launch path with the direct binary has fixed my problems.
: ${STEAM_RUNTIME:=1} export STEAM_RUNTIME
I think this is the problem: if you remove that part of the steam wrapper script (originating from https://github.com/anyc/steam-overlay/blob/master/games-util/steam-launcher/files/steam-wrapper.sh I think), then it'll probably work.
I can reproduce a similar failure on Debian testing by running STEAM_RUNTIME=1 steam or STEAM_RUNTIME=0 steam.
Historically, STEAM_RUNTIME=1 explicitly enabled the legacy LD_LIBRARY_PATH-based Steam Runtime (unnecessary, because it's the default anyway), while STEAM_RUNTIME=0 disabled it (unsupported/unsupportable, it's functionally necessary for the 32bit/scout client and older games). Unfortunately STEAM_RUNTIME had a slightly odd design where it was both an input and an output, so the pressure-vessel container framework also uses that same environment variable to detect whether it's been run in the wrong environment. A future update is likely to detect and ignore STEAM_RUNTIME=1 and STEAM_RUNTIME=0.
I think this is the problem: if you remove that part of the
steamwrapper script (originating from https://github.com/anyc/steam-overlay/blob/master/games-util/steam-launcher/files/steam-wrapper.sh I think), then it'll probably work.
Yep, just reproduced. Works as expected now thank you.
A future update is likely to detect and ignore
STEAM_RUNTIME=1andSTEAM_RUNTIME=0.
Good to know. Thanks for the help.
Opened https://github.com/anyc/steam-overlay/issues/386 to suggest that the wrapper script should stop setting this.
Making the container runtime machinery cope with STEAM_RUNTIME=1 (and maybe STEAM_RUNTIME=0 for completeness) is tracked as steamrt/tasks#1134 internally.
Running Steam with STEAM_RUNTIME=0 or on a purely 64-bit system continues to be unsupported; these might work if you're sufficiently lucky, but I don't recommend either of them.
Can confirm commenting out the following lines in /usr/bin/steam resolved the issue for me as well.
: ${STEAM_RUNTIME:=1}
export STEAM_RUNTIME
Back up and running with the steamrt3 beta.
The latest beta update includes a workaround for this issue.
The latest beta update includes a workaround for this issue.
Confirmed (not on Gentoo, but STEAM_RUNTIME=1 steam works now, and we're fairly sure that was the root cause).
I think we can close this issue now: unusually, we don't need to wait for the workaround to reach a stable release, because this regression only affected the beta.
The workaround can be replaced by a cleaner solution later, but that can be tracked internally and shouldn't make any difference to users.
SDL_VIDEODRIVER='wayland,x11,windows'x1 2026-09
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Steps for reproducing this issue:
steam-logs.tar.gz
I get the following when trying to start Steam in a terminal: