KDE Plasma 6.8: The Final Transition to Wayland and Removal of X11

KDE Plasma 6.8 will be the first release to completely remove the X11 session from the login screen and eliminate X11-specific code paths within Plasma Shell, System Settings, and device configuration. This move marks the end of a 15-year transition toward Wayland, allowing KDE developers to focus exclusively on a single code path to drive performance improvements, memory optimizations, and new feature development.

Transition Timeline and Scope

Plasma 6.8 is the target release for the removal of X11 support, expected in approximately five months.

To ensure users have time to migrate, Plasma 6.7 serves as the final release that includes an X11 session. Users currently on Plasma 5.27 or any version prior to 6.8 will not be affected, as these changes are not retroactive.

What is being removed

  • The X11 session option in the login screen.
  • X11-specific code paths in Plasma Shell, System Settings, and device configuration.

What remains supported

  • XWayland: Support for X11 applications remains intact, allowing users to continue running legacy X11 software within the Wayland session.
  • KDE Applications: KDE apps will continue to work on other X11-based desktop environments for the foreseeable future.
  • Plasma Login Manager: The manager will still be able to launch X11 sessions for other desktop environments.

Data-Driven Decision for Wayland Adoption

KDE's decision to retire X11 is based on internal metrics showing that over 95% of Plasma 6.6 users have already migrated to Wayland. This trend is mirrored in Sentry crash reports, which indicate that very few contributors are still testing or developing on X11.

While the overall adoption rate across all versions (including the long-term support Plasma 5.27) is approximately 76%, the developers note that Wayland was not the default in older releases, explaining the gap in adoption for those legacy versions.

Technical Challenges and Community Concerns

Despite the high adoption rates, the community has highlighted several critical gaps and regressions associated with the move to Wayland. These issues primarily center on accessibility, specialized workflows, and hardware compatibility.

Accessibility and Specialized Tooling

Some users report significant regressions in accessibility software. Specifically, voice input systems like Talon—which allow for window manipulation and script execution via voice—do not currently work on Wayland due to a lack of agreed-upon protocols.

Known Technical Gaps

Community members and documentation have identified several missing or broken features in the Wayland session:

  • Window Management: Lack of ability to save and restore positions of native Wayland windows, and the absence of a full-screen aspect ratio correction.
  • Session Management: Difficulty in restoring application states (e.g., Konsole tabs and Dolphin folders) across sessions.
  • Remote Desktop: A lack of headless RDP solutions, which remains a requirement for some professional workflows.
  • Global Menu: Lack of support for non-Qt applications.

Hardware and Driver Issues

Users with older NVIDIA GPUs (specifically Pascal architecture) have reported instability. Some note that the NVIDIA binary driver performs poorly with Wayland, while the open-source drivers may lack support for older hardware or require very recent kernels (6.19+) to avoid weekly crashes.

Community Perspectives on the Migration Strategy

While many users praise the smoothness and responsiveness of Plasma on Wayland, some developers and power users have criticized the "hard cut" approach of removing the codebase simultaneously with the feature.

"Disabling a feature AND simultaneously removing the codebase for that feature almost never ends well... a much better strategy is to first make the feature unavailable by normal means while still allowing a workaround."

Other users expressed concern over the loss of the ability to swap KWin for independent tiling window managers, a popular configuration in the X11 era that is more restricted under Wayland's compositor-centric architecture.

Sources