this post was submitted on 21 Aug 2026
45 points (97.9% liked)
Linux
67142 readers
1409 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Maybe it's arch based? Tested bazzite and found it overhyped, I don't think a immutable flatpak solution is the best for gaming. I use CachyOS on steam deck and love it's easy setup (easy for an arch user).
Bazzite uses the Steam rpm, not flatpak.
Though I think other launchers like Heroic may be flatpaks. But that's no different to SteamOS.
True, actual steam flatpak is a mess. Opensuse Kappa/Aeon actually use it and it took an afternoon of debugging and 3, barely - documented fixes to get proton games to launch at all.
I don't believe the Steam flatpak is responsible for those issues
openSUSE recently added some more security policies. By default, Wine cannot run normally. There's a package you can install that sets SELinux security policies to allow it to work. If you install the openSUSE Steam rpm, that security policy automatically gets installed too.
This is a downside of flatpak's approach to sandboxing. It aims to work everywhere on every distro, using bubblewrap instead of something like SELinux or AppArmor. But it also does not interact with AppArmor or SELinux, so if they block something, flatpak can't override that.
Meanwhile, snap uses AppArmor for sandboxing. So even if there was a policy like openSUSE's that prevented Wine from working by default, since snap speaks AppArmor, it can give itself the necessary permissions to make Wine work.
SELinux and Bubblewrap are two very different technologies. They could get out of each other’s way better, but you cannot “sandbox with SELinux”.
You absolutely can sandbox using SELinux. Red Hat even has a tool called "sandbox" for just that: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/chap-security-enhanced_linux-securing_programs_using_sandbox
Edit: and Android sandboxing is built heavily around SELinux: https://source.android.com/docs/security/features/selinux
Fair enough, you can do some sandboxing this way. But SELinux is not a sandboxing tool in the same way bubblewrap or landlock are. It’s a tool that can put gates around your tools until it’s a sandbox, but SELinux as sandboxing is not in the spirit of “tools doing one thing and doing it well”