Proton does not reliably work if installed on a BtrFS sub volume

protonclosed

ValveSoftware/Proton#6335 · opened 2022-11-23 by VortexAcherontic · updated 2022-12-11 · 1 comments · github

VVortexAcherontic 2022-11-23 github

Proton Version: 7.0-4
Games: Statisfactory, Age of Mythology

If Proton is installed on a BtrFS subvolume, in my case my entire /home/user/ is a BtrFS subvolume, it seems to be unable to create valid wineprefixes sometimes.
Moving Proton to a separate XFS partition allows it to operate as expected.

Steps to reproduce:

Install Proton on a BtrFS volume
Start a new game with a non-existend Proton prefix which has some Visual C++ Runtime dependencies
Game crash

Proton Log of Satisfactory with Proton on BtrFS volume: Gist-File
Furthermore this does not affect all games as this seems to be related to some Visual C++ runtime installation failures as Satisfactory is complaining about a missing C++ runtime if launched with Proton installed on the BtrFS volume.
grafik
This dialogue does not appear with Proton installed on a XFS volume.

Age of Mythology: Extended Edition Proton Log

Additional system informations:

Steam is installed via flatpak: Freedesktop.org SDK 22.08 (Flatpak runtime) (64 Bit)
OS: openSUSE MicroOS
GPU: nVidia RTX 3080
Driver: 525.53
DE: Gnome 43.1
Display server: Wayland

VVortexAcherontic 2022-12-11 github

Turned out it was SELinux who made things bit wired. I don't know why it ran from a XFS volume but after setting:

sudo setsebool -P selinuxuser_execmod 1

Proton operated as expected from a BtrFS volume, created a new prefix and installed all dependencies correctly.

Nothing extracted yet.