KDE Plasma 6.8 Drops X11 for Good: What Its October 14 Wayland-Only Release Means for Your Desktop
KDE turns 30 this October, and the project picked a genuinely consequential way to mark the occasion. KDE Plasma 6.8 is scheduled to ship on October 14, 2026, the same week as KDE's anniversary, and it does something none of the previous Plasma 6 releases have done: it removes the dedicated Plasma X11 session entirely. From 6.8 onward, a fresh Plasma install offers exactly one session at the login screen, and it is Wayland.
That is a bigger change than most Plasma point releases, and it lands squarely in territory this site has covered before from the GNOME and Ubuntu side. If you run KDE Plasma and you have any software on your machine that depends on X11 specifically, not just on X11 applications running correctly but on X11's older, more permissive access to the desktop itself, this release is worth understanding before you update.
What's actually changing
Plasma has offered both an X11 session and a Wayland session side by side since Plasma 6 launched in February 2024, with Wayland set as the default but X11 kept available as a fallback for anyone who needed it, whether for GPU driver quirks, remote desktop tools, or software built specifically against X11. Plasma 6.8 removes that fallback. According to KDE's own announcement, the X11-specific code paths inside Plasma Shell, System Settings, and the device configuration modules are being deleted outright, not just hidden or deprecated. Plasma 6.7, released earlier in 2026, is the last version of Plasma to ship a full, dedicated X11 session.
That does not mean every X11 program stops working the moment you update. Ordinary applications built for X11 keep running fine through XWayland, a compatibility layer already built into Wayland sessions that lets individual X11 programs open a window and behave normally without either the app or the user needing to know the difference. Web browsers, office suites, most games, and the vast majority of Linux software fall into that category, which is exactly why KDE expects this change to be a non-event for most users. The people who notice are a narrower group, running software that needs something XWayland was never built to provide.
Why KDE is doing this now, and why the date matters
KDE was founded in October 1996 by Matthias Ettrich, then a student at Eberhard Karls University of Tübingen, making it one of the oldest continuously developed desktop environments in open source software. Thirty years later, the project is marking that anniversary at its annual Akademy conference, held this year at Graz University of Technology in Austria, and Plasma 6.8's October 14 release date was chosen specifically to land during that same anniversary week rather than falling out of the ordinary release schedule by coincidence.
The timing gives the X11 removal a symbolic weight beyond the technical change itself. Wayland has been Plasma's default session since Plasma 6 shipped in 2024, and KDE has been steadily narrowing the gap between what X11 could do and what Wayland can do ever since. Dropping X11 outright on Plasma's 30th anniversary release reads as KDE declaring that transition finished, not just mostly done. It is a similar direction to the one GNOME took with Fedora 43 and Ubuntu 26.04, which we covered in detail in our look at Wayland becoming the default across Linux distributions, except here it is happening inside a single desktop environment's own release cycle rather than being driven by distribution-level packaging decisions.
What this means if you run Gloomia on a Plasma desktop
Gloomia's Linux build, whether installed from the .deb package or the AppImage, attaches to an X11 desktop session to render its wallpapers. That has been true of the Linux build since it launched, and it is the same constraint that already applies on GNOME desktops that have dropped their own X11 session, covered in more depth in our guide to what's actually different about Gloomia on macOS and Linux. On a KDE Plasma machine still running Plasma 6.7 or earlier, or on any Plasma session explicitly configured to use X11, nothing here changes: Gloomia works the way it always has, full catalog, full pricing, the same automatic pausing on battery power and fullscreen apps that the Windows and macOS builds get.
Once a machine updates to Plasma 6.8 and its Wayland-only session, there is no longer an X11 session on that desktop for Gloomia to attach to. XWayland does not change this, for the same reason it did not solve it on GNOME: XWayland's job is making individual X11 applications open windows correctly inside a Wayland session, not reproducing X11's older, more direct access to the desktop background layer that sits behind every window. A live wallpaper needs that background layer specifically, and Wayland's compositor model, KDE's implementation included, does not currently expose it to an X11 client running through XWayland.
If you are on KDE specifically and this matters to you, the practical move right now is the same one we laid out for GNOME users: stay on Plasma 6.7 for as long as you need an X11 session, since KDE has committed to keeping that session supported with fixes for roughly six months after 6.8 ships, or switch to a desktop environment that still defaults to X11 for the machine you actually want a live wallpaper on. Xfce, MATE, Cinnamon, and LXQt all still run on X11 by default and show no sign of following GNOME or KDE's lead on this in the near term.
The other genuinely new things in Plasma 6.8
Dropping X11 is the headline change, but it is not the only thing in this release, and it is worth separating the two, because most of what else is shipping has nothing to do with the session change at all. Plasma 6.8 turns on triple buffering for NVIDIA GPUs by default, which should smooth out some of the stutter NVIDIA users on Wayland have reported compared to open source GPU drivers. The new Union theming system, which KDE has been rolling out gradually across recent releases, extends in 6.8 to cover QtWidgets applications like the Dolphin file manager and the Kate text editor, on top of the QtQuick apps it already reached, so theme consistency across KDE's own apps takes another real step forward rather than staying Wayland-only in scope.
Kup, a backup scheduling tool that has existed as an optional add-on for years, becomes an official part of the Plasma desktop in this release. Plasma Browser Integration adds support for the Flatpak version of Microsoft Edge, closing a gap that previously only covered natively-packaged browsers. And a handful of smaller fixes round things out: reduced resource usage for the Trash widget, System Tray widgets now freeing their memory immediately when disabled rather than only after a restart, and Plasma launching with a plain background instead of failing outright if its wallpaper plugins are broken or missing.
How this compares to what happened on GNOME
The pattern here is familiar if you followed GNOME's own X11 removal. Fedora 43 dropped the GNOME on Xorg session outright, Ubuntu followed starting with 25.10, and Ubuntu 26.04 LTS carried that decision into its long-term support release. GNOME 51, which we covered in detail in our rundown of GNOME 51 "A Coruña", shipped on top of that Wayland-only foundation with features like a standard background blur API that assume Wayland is simply how the desktop works now, not one option among several.
KDE Plasma is following a similar arc, just on its own timeline and for its own reasons. The practical difference for anyone weighing a desktop environment switch is that, as of Plasma 6.8's release, GNOME and KDE both drop X11 as a default session choice within roughly a year of each other, while Xfce, MATE, Cinnamon, and LXQt have made no equivalent move. That makes the choice of desktop environment, more than the choice of distribution, the thing that actually determines whether an X11-dependent tool keeps working on a fresh install going forward.
What to actually do about it
If you are not currently running any software that specifically needs an X11 session, this release should be close to invisible, the same way GNOME's transition was for most people. Ordinary applications, browsers, office tools, and games all keep working through XWayland without any action from you. If you do run something that needs X11 directly, the most useful thing you can do before updating is simply check what session you are actually on. From a terminal, printing the XDG_SESSION_TYPE environment variable will tell you definitively whether a given login is x11 or wayland, which is worth doing before assuming a Plasma 6.8 update will or will not affect you.
For anyone specifically weighing whether to keep a Linux machine on an older Plasma release, a different desktop environment entirely, or move a live wallpaper setup to a different device, our guides on building a hacker-aesthetic Linux desktop and the general macOS and Linux differences breakdown are both good next reads, since they cover the rest of what's identical and what still varies across the three platforms Gloomia currently supports.
The bigger picture
Whatever you think of the timing, shipping the release that finally removes X11 during the same week as a 30th anniversary is a genuinely bold piece of scheduling, and it says something about how settled KDE now considers Wayland to be as a foundation rather than an still-catching-up alternative. For a project that started as one student's side project in 1996 and now ships one of the two dominant Linux desktop environments, retiring a two-decade-old display server on its own birthday is the kind of decision that only makes sense once a team is confident the replacement is actually finished, not just usable.
That confidence does not remove the real, narrow category of software still built around X11's older assumptions, live wallpaper tools among them. It just means the timeline for dealing with that gap now has a specific date attached to it: October 14, 2026, and roughly six more months of X11 support on Plasma 6.7 after that for anyone who needs the runway.
Frequently asked questions
When does KDE Plasma 6.8 release, and why that specific date?
KDE Plasma 6.8 is scheduled for October 14, 2026. The date was picked deliberately to land on KDE's 30th anniversary, marking three decades since Matthias Ettrich founded the KDE project in October 1996.
What exactly is changing with X11 in Plasma 6.8?
Plasma 6.8 removes the dedicated Plasma X11 session entirely. The login screen will only offer a Wayland session, and X11-specific code paths inside Plasma Shell, System Settings, and device configuration are being removed. Plasma 6.7 is the last release to ship a full X11 session.
Will X11 applications still work in Plasma 6.8 if the X11 session is gone?
Ordinary X11 applications keep working through XWayland, a compatibility layer that lets individual X11 programs open windows inside a Wayland session. What XWayland does not restore is direct access to the desktop background layer, which is a separate, stricter part of Wayland's design.
Does dropping the X11 session in Plasma 6.8 affect Gloomia?
Yes, in the same way it affects any live wallpaper tool built for X11. Gloomia's Linux build attaches to an X11 desktop session. On a Plasma 6.8 machine running the new Wayland-only session, there is no X11 session left for Gloomia to attach to, and XWayland does not expose the desktop background layer that a live wallpaper needs, so Gloomia cannot currently run there.
How long will KDE keep supporting the Plasma X11 session for people staying on 6.7?
KDE has said it plans to keep supporting the Plasma 6.7 X11 session with fixes until roughly early 2027, about six months after Plasma 6.8 ships, giving anyone who depends on X11 today a defined window to plan around rather than an abrupt cutoff.
What else is new in Plasma 6.8 besides dropping X11?
Plasma 6.8 enables triple buffering for NVIDIA GPUs by default, extends the new Union theming system to QtWidgets apps like Dolphin and Kate, folds the Kup backup scheduler into the desktop as an official component, adds Flatpak Microsoft Edge support to Plasma Browser Integration, and includes a round of resource-usage and system tray fixes.