Closed AesaraB closed 6 months ago
This was driving me absolutely insane trying to figure out, but if you find this issue then chances are it's not flatpak nor Steam that is your issue.
If you enable proton's debugging and read the log, you'll see something like
0009:err:virtual:map_file_into_view failed to set PROT_EXEC on file map, noexec filesystem?
This is because OpenSUSE MicroOS desktop derivatives (Aeon, Kalpa) have an issue with SELinux's default policy
From the OpenSUSE documentation:
If you run into issues using WINE, and WINE based programs in flatpaks, it is likely due to an SELinux issue, and can be checked by running: # sudo getsebool selinuxuser_execmod If that returns 'selinuxuser_execmod --> disabled', you will need to enable it. This can be done temporarily (resets on next boot) with # sudo setsebool selinuxuser_execmod 1 Or can be set Persistent with: # sudo setsebool -P selinuxuser_execmod 1
If you run into issues using WINE, and WINE based programs in flatpaks, it is likely due to an SELinux issue, and can be checked by running:
# sudo getsebool selinuxuser_execmod
If that returns 'selinuxuser_execmod --> disabled', you will need to enable it. This can be done temporarily (resets on next boot) with
# sudo setsebool selinuxuser_execmod 1
Or can be set Persistent with:
# sudo setsebool -P selinuxuser_execmod 1
Thanks @AesaraB, you saved my day!
This was driving me absolutely insane trying to figure out, but if you find this issue then chances are it's not flatpak nor Steam that is your issue.
If you enable proton's debugging and read the log, you'll see something like
This is because OpenSUSE MicroOS desktop derivatives (Aeon, Kalpa) have an issue with SELinux's default policy
From the OpenSUSE documentation:
Related issues: