- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Source: https://linux-hardware.org/?view=os_display_server
Reporting is done by users who voluntarily upload their system specs via
Source: https://linux-hardware.org/?view=os_display_server
Reporting is done by users who voluntarily upload their system specs via
Wayland has a mouse capture bug in proton / wine. It particularly seems to be an issue in FPS games. That may contributing to slower adoption for Linux gamers.
https://github.com/ValveSoftware/Proton/issues/7564
Works fine here, on mutter with mesa. Looks mostly like a KDE bug.
I don’t have that bug (KDE 6)
Speaking of Valve, they probably have numbers for Wayland vs X too, unfortunately they don’t seem to publish this statistic in their survey.
Valve is difficult. On the one hand they have their own Wayland compositor with gamescope. Which works by launching an explicitly configured XWayland session for the game.
And on the other hand there’s Steam, which is still an X application.
And on top of that are stupid Steam Input bugs that only happen when you try to launch a game with gamescope.
On the Steam Deck in gaming mode Gamescope is the main compositor which launches two XWayland sessions. I guess one for Steam and one for the game.
It’s bizarre.