#Plasma is going all #Wayland

After nearly three decades of KDE desktop environments running on #X11, the future KDE Plasma 6.8 release (due early 2027) will be Wayland-exclusive.

Read the FAQ below to find out what this means for you and the future of KDE:

https://blogs.kde.org/2025/11/26/going-all-in-on-a-wayland-future/

@kde This is great news to hear! 🎉
@kde Wayland, the thing that still has a lot of issues and poor compatibility? oh ​

@nube I understand where you're coming from, but there are two important things to note about this.

First, XWayland is NOT going anywhere. Almost all X11 apps will still work, they'll just run via XWayland instead of refusing to run.

Second, I do agree that Wayland protocol discussions have become "circular". That's is annoying and it should 100% be reworked to allow for more use cases.

@nube @kde and what are those issues and poor compatibility, if I may hear?
@kde I am a bit nervous given upstream Wayland protocol discussions have... Gone circular again, but if they finally add global positioning support to KWin before Plasma 6.8 releases, I think 98% of users will be fine.
@kde uh-oh. I still switch my desktop to X11 when going away because I could never get Nomachine to work with kwin_wayland. Well, maybe krfb is/will finally stable enough to use, will have to check.
@virtulis @kde krfb works great for me. For what it's worth

@virtulis @kde I'm pretty sure NoMachine was one of the first of these types of solutions to actually work on Wayland, and it generally worked fine at least as far as three years ago (I used it myself, but probably not all features). Maybe you encountered a specific bug or something related to your setup?

Having said that, I recommend Rustdesk for this.

@herzenschein probably, although it's been quite persistent. Might be an Arch-specific issue too (the libnxegl it puts in LD_PRELOAD segfaults randomly, which it probably isn't supposed to do!)

Rustdesk didn't work for me either when i tried, but that was a while ago. Thanks for reminding!

@kde That’s good news, X11 is pretty much unmaintained after all.

Hoping to see a push to get rid of the remaining bugs/holes left from the transition so it all gone by 2027. I’ve been stable on Wayland for years now, but I don’t venture into some of the problem areas.

Good luck!

@kde Fun. My laptop doesn't work right under Wayland. Thanks for fuckin it up
@hellomiakoda Please share some details instead of being passive aggressive. There's still a lot of time to fix your issues.
@hellomiakoda @kde Ive noticed that many issues people have are related to old systems or just people unaware that things work under Wayland now. What are your issues?
@frd @kde Remote desktop doesn't work, performance issues, and crashes.
@hellomiakoda @kde Hopefully the remote desktop issue will be fixed till then... as for "performance issues" and "crashes" please be more specific. And do report them so they'll get fixed till them as well. People are working on making things better.
@frd @kde That's great and all. What I'm pissed about is getting pushed to something that doesn't do what it's predecessor does. Could've left both till wayland worked just as well, but nope, all the distros are forcing a change over. If I wanted to be forced on to still broken shit, I'd run Windows.
@hellomiakoda @kde Both were left until it wasn't sustainable anymore. Now focus is on Wayland. Things will get better. As mentioned in the post, one can use an LTS version like Alma Linux till 2032. Anyways this will only happen in 2027. So much time ahead, Things change, heck we will also change till then. All is good. No need to get pissed.

@hellomiakoda @frd @kde have you realised that these things bugs are specific to you, and rare? I'm sorry volunteers don't want to keep maintaining broken-by-design x11.

Instead of being entitled, you could also just ask for help normally. Seriously, not everyone have the same issues as you...

@hellomiakoda @frd @kde the remote Desktop part is wa annoyes me the most. Ive spend a whole week end Debugging that till i found that out, still makes me angry.
@kde Does this mean that we will have full colour management support with wayland by then? There are some efforts and kde is really far ahead with this, but limited by wayland itself which is really bad at the moment... actually unusable...
@clerian @kde what do you mean "full colour management"?
@a_blahaj @clerian Didn't X11 not have good color management or HDR support to begin with?
@cameron_bosch @a_blahaj X11 does support colour management - e.g. different input/output and working profiles for different applications + multi screen setups. This is really difficult to do in wayland - compare https://discuss.pixls.us/t/wayland-color-management/10804 for more details. This is not about HDR.
Wayland color management

Just saw the following on the wayland developers mailinglist HDR support in Wayland/Weston and that reminded me that I always wanted to make a topic here to discuss color management on wayland, especially since the proposal from the wayland devs itself[1] is lacking in a few aspects, namely It is missing profiling/calibrating support which in contrast to what the wayland dev thinks is not an orthogonal problem (IMHO) Not all applications actually use ICC (anything that uses OCIO for example) s...

discuss.pixls.us
@clerian @kde It's already done and fully implemented in KDE Plasma. Applications have just started to use it.
Will we still be able to design / customize / distribute sddm login screens, plasma splash screens and boot splash screens? @kde
@vitordematos @kde I mean, I don't see why you wouldn't be able to? They work fine on wayland.

SDDM might be replaced by then though.
@vitordematos @kde Yeah, Plasma Login should be out by then.
@vitordematos @kde Why wouldn't you? That's not a display system-specific thing. Nothing changed there.
@kde oh no this is all we'll hear about from @felimwhiteley for the next 12 months
@kde
I do, every now and then, run CmapTools (a conseptmap esitor that I like). It is writen Java, And my install of it does not run on Wayland.
😠
Yup, smal hickup for me. I do not know if it has fresher version, that runs on Wayland.
@jorshmin @kde XWayland?
@sandro @jorshmin @kde xwayland is a compatibility tool to run x11 apps on wayland.
@kde Done some reading fro several sources, and did find that xwayland is installed as default in kubuntu 25.19. yet CmapTools does not start on wayland instance, even if xwayland should be activated by kubuntu 25.10 update.
kari@Coruscant005:~$ inxi -F | grep -e Desktop -e Display
Desktop: KDE Plasma v: 6.4.5 Distro: Kubuntu 25.10 (Questing Quokka)
Type: Desktop Mobo: Gigabyte model: B450 AORUS M
Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.6 driver: X:
@kde what did you to to konqi 😭
@kde K Desktop Environment desktop environments
@kde I know Nvidia is bad and greedy, and they shouldn't impact our software ecosystem, and those who buy their GPUs and use Linux know what they're signing for, and etc etc


But recommending nouveau is disingenuous.

@a1ba @kde The problem is that Nvidia is the only one who can fix the Maxwell and Pascal reclocking issues.

Unless somebody wants to play Russian Roulette with the propietary drivers.

@cameron_bosch @kde so you literally didn't read my comment.

It also isn't "just" the reclocking that stops nouveau but overall state of it. Last time I tried it, it couldn't even produce the correct image.

Well, I don't want to blame nouveau developers for that and all it's troubles is on Nvidia but I also wouldn't recommend nouveau to the average Joe because Joe doesn't care.
@a1ba @kde they only recommend nouveau for old cards? where it does generally work
@chjara @kde Pascal can be considered old now
@kde please for the love of god make a Wayland full size keyboard I don't want to use x11 anymore
@wafflesies @kde I noticed maliit was deprecated on Arch Linux. Could they be close in terms of their new on screen keyboard?
@cameron_bosch @kde idk I'm on artix and I can build plasma-keyboard but it won't launch. It's currently in development

@wafflesies @kde That's strange then.

Why would they deprecate Maliit before Plasma keyboard was ready?

@cameron_bosch @kde idk that sounds like an arch thing
@wafflesies @kde There is a new on screen keyboard in the making if that's what you mean.
@fell @kde yes! Im excited for iti just can't get it to launch right now lol
@wafflesies @kde The article links to the `Known significant issues` page, which mentions that KDE is working on a new virtual keyboard:
https://invent.kde.org/plasma/plasma-keyboard/
@hooly @kde yeah ik I've been talking to them about it
@kde not reading the text in this post and pretending it means you're sunsetting wayland and switching to plan 9 rio
Isn't wayland limited in terms of accessibility features?

@Martineski @kde Yes, but so was X11. Most of it was barely working under X11 as well.

Orca, for example, barely works even in 2025 on X11.

Oh, that sucks. I hope things improve with time, O7.
@Martineski @cameron_bosch redhat hired someone to work fulltime on modernizing the accessibility framework, which is more about the toolkit than the way pixels are rendered, so its getting back into shape after a long time on life support
@Martineski @kde On KDE Plasma, pretty much all the existing accessibility features are available on Plasma Wayland. If there's an issue with accessibility for you, please file a bug report about it!