New Steam runtime: Proton 5.13-1 breaks in Silverblue (bwrap: Can't mkdir /usr/lib64/gconv: Read-only file system)

Project Discussion
1

The new proton release and Steam runtime (soldier) break on every game start via Steam with the following log in Silverblue:

bwrap: Can't mkdir /usr/lib64/gconv: Read-only file system
ln: failed to create symbolic link '/run/user/1000/SteamLinuxRuntime.4297668b2bb5059a/socket' -> '': No such file or directory

I’ve not found a workaround except disabling the runtime yet.

EDIT: Still debugging the issue. Maybe this is not the root cause.

Available workaround: Proton 5.13 forces Steam Linux Runtime -> No MangoHud · Issue #369 · flightlessmango/MangoHud · GitHub

1 Like
2

use flatpak steam, not rebase system

3

The flatpak steam has limitations which make it not an alternative for me as of now. The new Steam runtime is not able to run inside flatpak (Proton 5.13-1 doesn't run with Flatpak Steam · Issue #294 · ValveSoftware/steam-runtime · GitHub) (yet) and SECCOMP is not supported in flatpak which breaks some Denuvo games (PROTON_USE_SECCOMP=1 does nothing · Issue #608 · flathub/com.valvesoftware.Steam · GitHub). I’ll continue to keep an eye on it.

1 Like
4

The new runtime is not a runtime, but a container solution similar to flatpak in some regards. Not compatible in the meantime.

5

just need to be patient, as always.

6

As an alternative you may want to consider adding a community runtime option for proton inside steam from flathub.