[Steam RT3] Internal error: _srt_architecture_read_elf

[alosarjos]

Your system information

• Steam client version (build number or date): 1789086785
• Distribution (e.g. Ubuntu): Arch Linux
• Opted into Steam client beta?: Yes
• Have you checked for system updates?: Yes
• Steam Logs: steam-logs.tar.gz
• GPU: AMD

Please describe your issue in as much detail as possible:

Just have Steam opened and checked for system logs. I see the message:

steam[12374]: pressure-vessel-wrap[12892]: Internal error: _srt_architecture_read_elf: assertion 'error == NULL || *error == NULL' failed

[kisak-valve]

I saw this the other day without SteamRT3. Seemed benign.

[smcv]

This is a minor bug in error-handling, which can randomly happen if Steam starts two containers with the same runtime in parallel (most likely to happen as a result of routine background tasks being run under Proton, I think). I also noticed it during development and already fixed it in steam-runtime-tools!1056, so it should get fixed in the next beta - I'm not 100% sure whose beta, most likely it's the various "Steam Linux Runtime" compatibility tools that are logging this warning, but possibly a new Steam Client beta might be needed for a complete fix.

It's probably harmless on x86. On ARM devices with FEX emulation, it could potentially interfere with container setup (I'm not sure exactly, fixing it was easier than figuring out its worst-case impact).

[smcv]

If you use up-to-date versions of Proton, then I think this is most likely to be coming from Steam Linux Runtime 4. If you opt-in to the beta branch of the Steam Linux Runtime 4 tool, this issue should go away after the beta gets updated to 4.0.20260914.x or later (hopefully coming soon, but I can't predict a specific date).

If you use older versions of Proton, you might also need Steam Linux Runtime 3.0 (sniper) version 3.0.20260914.x, or even Steam Linux Runtime 2.0 (soldier) version 2.0.20260914.x, which will probably be published as new betas around the same time as for SLR 4.

If you'd like to try out the fixed version in advance, you could download and unpack https://repo.steampowered.com/pressure-vessel/snapshots/0.20260914.0/pressure-vessel-bin.tar.gz in some convenient location (I usually use ~/tmp for this), then run Steam as

PRESSURE_VESSEL_PREFIX="$HOME/tmp/pressure-vessel" steam

replacing $HOME/tmp/pressure-vessel with the appropriate path.

[smcv]

This is fixed in SteamLinuxRuntime_4 4.0.20260914.260627, SteamLinuxRuntime_sniper 3.0.20260914.260626 and SteamLinuxRuntime_soldier 2.0.20260914.260629, all released as new betas today.

An equivalent change for steamrt3c (used in the Steam Client) should be in a future beta, but this probably won't happen there anyway, because I can't think of a situation where we would start up two steamrt3c containers at the same time.