Doesn’t KDE kinda have that same refresh rate issue on Wayland? I remember seeing a bug that Qt has a limitation in this regard, In the video I saw the workspace transition ran at the lower refresh rate when multiple monitors were used.
Thankfully I stopped using multiple monitors so I can’t personally confirm.
Personally, I wouldn’t recommend Vanilla OS.
That’s a lot of churn and issues for such as young project that advertises itself to new users.
Wonder how much of that is going towards Hyprland: https://omarchy.org/news/2026/08/omacom-foundation-to-be-exclusive-hyprland-sponsor/
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
I don’t believe flatpak is directly responsible for Steam’s issues.
I believe that’s because 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.
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.
Bazzite uses the Steam rpm, not flatpak.
Though I think other launchers like Heroic may be flatpaks. But that’s no different to SteamOS.
I don’t think so, this still would let them host it so long as don’t have a “competing fork”. I’ve heard of licenses like Server Side Public License (SSPL) that do you what you say. Basically, that license requires all the infrastructure around the software to be open source to. So something like AWS couldn’t host the software without first open sourcing all their infrastructure.
Wayland wants to avoid problems that X11, Windows, and MacOS have. It deliberately avoids some “features” that application developers expect. A lot of it relates to security and privacy.
An example is that a window does not know where it is positioned on your screen and it cannot choose where to place its windows. Personally, I love this behavior. It means I can open an open and it opens in a consistent location (for most Wayland compositors, that’s centered on the screen). But others don’t like that. They would like the app to control where it opens; for some apps (a niche nowadays) you may have an application window and multiple more supporting windows, but on Wayland, they would all just get opened on top of each other rather than being placed around the main window.
Overall probably closer to the truth.
I wish people didn’t obsess over these large numbers as much. Like when Linux suddenly hit 5% on Steam when that was clearly just an outlier and was destined to fall right back down.
Phoronix’s more real world testing didn’t have Gnome performing badly: https://www.phoronix.com/review/cachyos-desktops-july-2026