http://bugzilla.opensuse.org/show_bug.cgi?id=1206292 Bug ID: 1206292 Summary: Wine/Proton not working relaibly with default SELinux configuration Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: vortex@z-ray.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 863450 --> http://bugzilla.opensuse.org/attachment.cgi?id=863450&action=edit Proton Log file if running from a BtrFS volume Hey there, this is a bit of a wired issue I was facing and first thought Proton/Wine to be the issue if running from a BtrFS subvolume but turned out this to not be the case. So here is the situation I faced with only some games: Running a game with Proton or Wine installed in my $HOME which is a BtrFS volume by default on MicroOS caused it to sometimes fail to install some dependencies into a new prefix. Often this seemed to have been related to C++ runtime stuff Wine/Proton will install for some games. It failed to install those and the game where unable to operate properly. My first quick fix was to move Proton to an XFS drive by creating a new SteamLibrary for the Flatpak Steam Client and moving Proton there. Afterwards it operated successfully with no issues. Later on however I've read someone���s review of MicroOS mentioning he had to set: sudo setsebool -P selinuxuser_execmod 1 To make Proton work reliable. I tested this for myself with affected games and can confirm this worked. Additionally also Bottles, Lutris and Heroic Games Launcher where affected by this issue and randomly did not operate successfully when running games via their own Wine runners. The above SELinux config change fixed it also for them. Games I experienced to have issues with the missing SELinux config: - Satisfactory (Steam) - Control (Heroic Games Launcher, EGS version) - Creature in the Well /Heroic Games Launcher, EGS VVersion) - Age of Mythology: Extended Edition (Steam) In case some wants to counter test this. Would it be an issue if the above SELinux configuration could be set as it by default on MicroOS to make the gaming workload work OOTB? Or are there any reasons some should not change the above configuration. In that case I'd like to know why. Kind regards, V. -- You are receiving this mail because: You are the assignee for the bug.