KDE turns 30, and its next release finally drops X11 for good

Why it matters: X11 has been the foundation of Linux desktop environments, including KDE, for decades. Plasma 6.8 completes a shift that's been building for years, moving fully to Wayland, a newer display protocol designed to replace X11's aging architecture.

The previous version, Plasma 6.7, still let users choose an X11 session if they wanted it. Plasma 6.8 removes that option entirely, requiring Wayland for the core desktop session going forward.

• Plasma 6.7: X11 session available as an optional choice.
• Plasma 6.8: X11 session support removed entirely.
• X11 apps: continue working through XWayland, a compatibility layer, even without a native X11 session.
• Full X11 series support: continues in the separate Plasma 6.7 branch into early 2027.

By the numbers: internal KDE data shows more than 95% of Plasma 6.6 users had already switched to Wayland before this change even happened. That's a genuinely strikingly high adoption rate for a purely voluntary migration, suggesting most of the KDE community made this switch well ahead of the software forcing it.

In real life think of it like a city finally shutting down an old subway line that almost everyone had already stopped riding. The change feels dramatic on paper, but most commuters made the switch to the new line a while ago.

Background: X11 dates back even further than KDE itself, first appearing in 1984 and standardized as X11 in 1987. It became the foundation nearly every Unix and Linux desktop was built on for decades. But security simply wasn't a major design consideration back then, and that's caused real problems as computing needs changed.

Specific, well-documented flaws include the ability for any X11 application to keylog the entire system, capturing keystrokes from completely unrelated programs, and to take screenshots of other running windows without permission. X11 also doesn't encrypt communication between the client application and the display server by default, meaning that traffic could be intercepted on a network. One font server vulnerability dating back to 1991 wasn't even discovered until 2014.

Why it matters: Wayland was built specifically to close these gaps. It isolates each application so one program genuinely cannot spy on or interfere with another, with the operating system's kernel enforcing that separation directly rather than relying on the display server to police it. That's a fundamentally more secure design than anything X11's original architecture was built to support.

Who's affected: if you don't run Linux, this doesn't touch you directly. But if you do use a KDE-based Linux distribution, like Kubuntu or openSUSE with Plasma, this is a meaningful under-the-hood change even if your day-to-day desktop looks almost identical.

Your applications should keep working the same way, since XWayland handles compatibility for anything still built specifically for X11. The bigger shift is architectural: Wayland handles graphics rendering, input, and security differently than X11 did, generally with better security isolation between applications and smoother handling of modern displays.

Background: KDE was founded in 1996 by Matthias Ettrich, then a university student frustrated that Unix desktop applications didn't look, feel, or behave consistently with one another. His original pitch wasn't just for a set of apps, it was for a coherent desktop environment where things worked the same way across the board.

That original vision, spurred by little more than a Usenet newsgroup post, quickly drew around 40 volunteer developers and became one of the two dominant desktop environments across Linux distributions, a position it's held for most of the three decades since.

By the numbers: KDE Plasma holds roughly 40% market share among Linux desktop environments, making it the single most-used option, ahead of its longtime rival GNOME at around 25%. That's a genuinely dominant position within its category, even if most computer users outside the Linux world have never heard of either.

The two projects take deliberately different approaches. GNOME favors a simplified, minimalist interface that hides most configuration options to keep things calm and focused. KDE Plasma does close to the opposite, exposing nearly every setting and panel option so users can customize their desktop as heavily as they want. Distributions like Kubuntu and openSUSE default to KDE, while Ubuntu and Fedora default to GNOME instead.

Why it matters: that customization philosophy is directly relevant to this X11 transition. A community built around wanting maximum control over their desktop is exactly the kind of user base likely to have strong, vocal opinions about losing an option, which helps explain why community X11-preservation forks emerged so quickly once the removal was announced.

The catch: not everyone is ready to let go, and the open-source community's response has been exactly what you'd expect: forking the old approach rather than accepting it disappears entirely.

Projects like Trinity Desktop Environment maintain their own fork of the older Qt3 toolkit specifically to keep an X11-based KDE-style desktop alive. A newer project called Sonic Desktop maintains its own fork of KDE's window manager specifically to retain X11 support. There's even a nostalgia project called Klassik, recreating the KDE 3 desktop experience, discontinued back in 2008, using entirely modern Plasma 6 and Qt 6 technology underneath.

What's next: that pattern, official support moving forward while community forks preserve the old way for holdouts, is common across long-running open-source projects. It means Plasma 6.8 dropping X11 doesn't mean X11-based KDE desktops vanish completely, just that they move outside the officially maintained project.

• If you don't use Linux, this doesn't affect you at all. It's purely a change to the technical foundation of one desktop environment.
• If you use a KDE-based Linux distro, expect your desktop to keep working normally, with better underlying security and display handling thanks to Wayland.
• If you specifically rely on X11-only software or workflows, community forks like Trinity Desktop Environment remain available, just outside the main KDE Plasma project.
• This is a useful example of how mature open-source software modernizes, letting the vast majority move forward while ensuring holdouts aren't simply abandoned.