- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
Prominent KDE developer Nate Graham put out a blog post today reaffirming the KDE Plasma’s intent that Wayland is their main focus and X11 support continues to be maintained but eventually it will go away. Nate Graham also noted around 73% of KDE Plasma 6 users are already using the Wayland session.
You must log in or register to comment.
Wayland! hisses vampiricly and claws at the light
Oh eventually I’ll get on board.
Remaining 30% probably people like me whose nvidia driver multi monitor issues make wayland unusable.
Yes, some multi monitor configurations work, yes, yours might work just fine, but there’s plenty of recent posts on kde.org forums showing the issue is far from isolated.
Multi monitor has issues in KDE itself as well, I’m on AMD and there are a few really annoying (and confirmed) bugs when it comes to multi monitor setups. Some bugs go waaaaay back.
Sadly nothing is being done about it.
I love this comment. I love it because even though I don’t know what wayland is, I gather by context it’s popular, and has something to do with output of your display.
And it’s popular, but it doesn’t work FOR YOU.
And you have to point out that just because something works for others, doesn’t mean it works for everybody.
I’m pretty unskilled when it comes to linux, but I’ve noticed linux users fall into one of two groups.
First, the group who genuinely want to help you. They may not KNOW the exact answer, because they don’t know your exact hardware, but they try to help with common problems.
The other group takes it as a personal insult if you’re having problems in linux that you don’t know how to solve. Like linux is part of their personality, and they think linux is perfect without the ability to have problems. Therefore the guy asking for help is just trying to insult linux, and therefore themselves. They then respond with hostility and personal insults about how it’s your problem.
Yeah. It IS my problem. Can ya figure out what I’m doing wrong?
But they don’t see it that way. In their eyes, linux is perfect, and you’re an asshole for saying you have an issue.
So what I’m saying is, I love how you already know you need to state upfront you KNOW it works for others, but not for you.
There are two groups of Linux Users.
Those who have a nice seamless experience, and those who have Nvidia GPUs
Oh don’t worry it’s not limited to Nvidia GPUs.
Last I even bothered trying Wayland, it still could not even start up a functional full desktop session on an Intel mobile iGPU.
Touch support really needs some love because OOF. I understand why it’s maybe not a priority, but I have a nice little 2-in-1 and I’m tired of pretending like tablets don’t at least deserve their niche.
Any good gesture support software I might be missing?
https://wiki.archlinux.org/title/Touchscreen#Wayland/Weston
If I’m reading the wiki correctly, touch is just reduced to pointer input and yeah, that’s exactly what it feels like
EDIT:
Yes, the writing is on the wall. X11’s upstream development has dropped off significantly in recent years, and X11 isn’t able to perform up to the standards of what people expect today with respect to support for multi-monitor setups, high DPI monitors, HDR, VRR, other fancy monitor features, multi-GPU setups, screen tearing, security, crash robustness, input handling, and more.
I glossed over it on first reading, but I guess there’s a small nod to it there and that’s something.
Tbh 73% is low for something as important as a thing you’re going to basically enforce. Get to 90% and then we can talk.
From what I read, it was originally higher (82%), but went down because SteamOS has X11 as its default.
You can read more about KDE X11 plan on here: https://pointieststick.com/2025/06/21/about-plasmas-x11-session/
Quoted from the blog: "Current status: Plasma’s X11 session continues to be maintained.
Specifically, that 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. "
That is good. I really like that approach.
I have 2 computers with KDE which I’ve been using for the past 6 months or so. I recently read about how to switch to Wayland (log out, find the option, log back in). Both of my computers were using X11, not sure why. Maybe I chose that during installation.
I switched both to Wayland and I’m going to do my best to stick to it. One of my computers has an older Nvidia card but luckily I don’t seem to have any problems.
Purely anecdotal, but maybe a large part of the 27% using X11 don’t even know the difference.
X11 is the default. For Plasma 6, so you didn’t choose it that’s just what it was.
Bit chicken and egg though, isn’t it? Maybe a big desktop environment enforcing Wayland will get people working more on the fixes for the stuff that doesn’t work out yet.
I understand people being annoyed if they are in the 30% though, and not trying to dismiss that.
Maybe a big desktop environment enforcing Wayland will get people working more on the fixes for the stuff that doesn’t work out yet.
Not really or at least not enough.
Of course they’re not going to drop it while it’s still at 73%.
We’ll see about that one.
No you won’t.
They won’t throw more than a decade of work to the garbage because “30%” and Nvidia. Those issues can be fixed. Want them to be fixed? Stop complaining and contribute.
Honestly just buy a machine that has issues with Wayland and daily it yourself.
We’ll make sure Plasma continues to compile and deploy on X11.
As for when Plasma will drop support for X11? There’s currently no firm timeline for this, and I certainly don’t expect it to happen in the next year, or even the next two years.
Note, they said “compile” and “deploy”, not “function” or “work”.
That’s basically “#vibecoding on release” talk.
