Steam still uses Xwayland on a Wayland desktop, and that can cause issues. Why hasn't it moved to native Wayland, and is a native build being worked on?
Why does Steam still rely on Xwayland?
Answers
Running an X11 application on a Wayland desktop is exactly what Xwayland is for. Steam using it doesn't mean the whole desktop has to use X11. KDE Plasma can run as a Wayland session while Steam's desktop windows are handled through Xwayland.
That compatibility layer can still have quirks, but shipping a Wayland desktop and keeping an X11 client are not mutually exclusive choices.
Reply to this answer
A native Wayland client isn't necessarily a switch you flip. Window handling, input, scaling and other desktop integration can depend on the application's existing X11 code and the libraries it uses. Changing that needs implementation and testing across different Wayland compositors.
Xwayland lets existing software keep working while that work is unfinished or not prioritized. That explains why the arrangement is possible, though it doesn't establish Valve's particular plans or priorities.
Reply to this answer
It's worth separating the Steam desktop client from the games it launches. A game can use a different windowing path from the client, so a native Steam window alone wouldn't guarantee that every game avoids Xwayland.
Reply to this answer
The supplied discussion doesn't establish whether Valve is working on a native Wayland build or when one might arrive. Without a current announcement or other reliable update, I wouldn't assume either that it's imminent or that it has been ruled out.
Reply to this answer
Add your answer
Answers are reviewed before publication.
shmupContinue!Caper:
Native Wayland also wouldn't automatically fix every Steam or game issue. The source of the problem could be elsewhere.