KDE developers confirm Plasma will continue having a maintained X11 session, and now we know Kubuntu will be Wayland by default.
On the KDE side, developer Nate Graham wrote a blog post to note that "Plasma's X11 session continues to be maintained". Graham said this means:
- We’ll make sure Plasma continues to compile and deploy on X11.
- Bug reports about the Plasma X11 session being horribly broken (for example, you can’t log in) will be fixed.
- Very bad X11-specific regressions will probably be fixed eventually.
- Less-bad X11-specific bugs will probably not be fixed unless someone pays for it.
- X11-specific features will definitely not be implemented unless someone pays for it.
However, the future is still very clearly Wayland-focused. There's no timeline for when Plasma will drop X11 support as it's still years away, but it will happen eventually. There's still a number of significant issues they're working through.
KDE's own stats show that "73% of Plasma 6 users who have turned on telemetry are using the Wayland session". Again, this is why telemetry is useful, it can show developers where they need to actually focus, it's not the bad word many seem to think it is.
As for Kubuntu, as confirmed by developer Rik Mills in reply to a user question about shipping a Wayland-only session (cheers, OMGUbuntu):
Yes, we have recently split the plasma sessions out into 2 separate packages, plasma-session-wayland and plasma-session-x11. At the moment we intend to ship the wayland one by default on the ISO and installs, while users who still want an X11 session will be free to install the X11 one.
Not surprising, with Ubuntu proper firmly moving to Wayland.
I get the point of "we have to move forward", but I'm still hit with very casual things that are not working that great with KDE on wayland that are not an issue in X11. Such issues include proper clipboard integration (I know there's ongoing work regarding that, in particular with xdg-portal), some apps having issue with their contextual menu showing nowhere near where they should, some screen-specific application being unable to know/settle on a specific screen, etc.
I'll keep checking on the regular; it's trivial to move from one to another after all, no configuration required. But it remains important to keep that option as long as very common issue can still show up.
Again, this is why telemetry is useful, it can show developers where they need to actually focus, it's not the bad word many seem to think it is.
Ugh. Telemetry driven development is the bane of my computing life. It insidiously causes some devs to use it as a substitute for actual thinking instead of as a support.
do you have any dev experience?
telemetry IA super useful, especially on case of limited resources...
Ugh. Telemetry driven development is the bane of my computing life. It insidiously causes some devs to use it as a substitute for actual thinking instead of as a support.I doubt that's the case here. And in open-source, it's absolutely vital, since you don't get to interact with your user-base otherwise, except through forums/discord, which carries an enormous bias (the only people who interact this way will be technically-focused anyway, while your "normal" goes unnoticed, which is especially likely now that the SteamDeck has jumped into so many non-techie lives).
This article has reminded that I turned user-feedback off when I last installed, thinking that I'd turn it on later. And I forgot to do so! It's now on, at one setting lower than maximum. Nice wee app, integrated into Settings.
About telemetry, I have no issues with it, as long as it's opt-in (not opt-out), being made clear what data is being transmitted, no personal data is collected, and it is assured that not one bit of data will ever be used for any purposes other than improving the software. Being a developer myself I do understand the value of such information, and not every time software is "phoning home", it's for evil purposes.