# Wayland vs X11 in 2026: what changes when you migrate on Linux

> KDE Plasma 6.8 retired the X11 session on October 14, 2026. The criteria for migrating to Wayland on Linux, what breaks and what the compositor decides.
> By José Maldonado · Technology · 2026-10-19

The KDE project released Plasma 6.8 last October 14 and with it closed the door to the desktop's X11 (Xorg) session, on the day the project turned 30. The login screen no longer offers the Xorg entry, which was the last safety net for anyone carrying an old-school workflow. X11 programs still start through XWayland, but the desktop that hosted them is gone, [as we reported in the farewell to X11](https://observatorioblockchain.com/en/technology/kde-plasma-68-30-aniversario-union-wayland/).

The move arrives with the ground already prepared. GNOME 50 removed its X11 session in March 2026, and Ubuntu 26.04 LTS, released in April, offers only Wayland on its default desktop. The [latency measurement NVIDIA presented at XDC 2026](https://www.muylinux.com/2026/10/06/nvidia-prueba-latencia-wayland-x-org/), held in Toronto from September 28 to 30, points in the same direction: using a photodiode and a microcontroller, engineer Kamil Łysik found no clear winner, and XWayland no longer adds the extra frame that used to hold games back.

What remains is the part no announcement resolves, and it is the part that decides your case: what breaks when you switch sessions. The answer does not depend on the protocol, but on the compositor you use, the GPU driver and whether your tools request global access to the keyboard or to the pixels of other windows. Plasma 6.7 is the last version with an X11 session and will keep it until early 2027, so migrating is not urgent by decree. It is worth knowing what it takes down with it before touching the login screen.

## X11 is not being switched off; what is being retired is the session

What KDE has removed is the session type, not application support. Since Plasma 6.8 there is no Xorg entry that starts KWin on the X server, while XWayland remains alive as an X server running as a client of the compositor and drawing each X11 window inside the desktop. Your veteran programs open as before, including those that will never have a native version, and KDE has confirmed that its applications will continue to support X11 for the foreseeable future.

What you lose is the session as such, with its central X server and its global access model. The desktop starts and programs open, so the migration is deceptive: the gaps are in the tasks that on X11 you solved without thinking and that now depend on a portal or an extension.

## Does staying on X11 still make sense?

For some users, yes. The clearest case is old hardware: drivers from the 470 branch and earlier do not support Wayland, and below that branch there is no accelerated XWayland either. With legacy drivers, Xorg is the only way to make use of the GPU.

The second group is desktops that are still born on X11: in 2026 Xfce, MATE, Cinnamon and LXQt still start with Xorg by default, each at a different pace toward Wayland. Even so, staying has an expiration date: Xorg has been in maintenance mode for years and those who delay migration will not find a better protocol, but fewer tested combinations.

## A map by desktop and by version

The useful question is no longer which distribution you come from, but which specific version each machine brings. The same Ubuntu 26.04 may or may not offer an X11 session depending on what you install on top, and the answer changes every six months. This is the picture as of October 2026.

Desktop

X11 session in October 2026

What you should know

GNOME 50

Does not exist

Removed support in March 2026; X11 apps go through XWayland

KDE Plasma 6.8

Does not exist

6.7 is the last with a session, supported until early 2027

Enterprise LTS

Yes

AlmaLinux 9 keeps the X11 session with support until ~2032

Xfce

Yes, by default

Stack ported to Wayland at a good pace; the window manager lags behind

MATE and LXQt

Yes, by default

Ports underway, no public date for a mature session

Cinnamon

Yes, by default

Its Wayland session is moving toward no longer being experimental

There is no day when X11 disappears from the computer, but fewer and fewer desktops offer it as a first-class option, and the handover is marked by LTS versions rather than headlines. GNOME 49 disabled it by default in September 2025 and GNOME 50 finished the job in March 2026, [according to the release chronicle](https://www.theregister.com/software/2026/03/19/gnome-50-debuts-with-x11-axed-wayland-front-and-center/5224877). Plasma arrived two versions later because it kept the code until 6.7.

## What breaks when you switch sessions?

The list of breakages is not long, but it is concrete and concentrates on the tools that on X11 took for granted an access that Wayland denies by design. Any of these areas deserves a test before moving the session on your main machine.

Area

What you did on X11

What exists on Wayland in 2026

Global shortcuts and push-to-talk

Any process captured keys regardless of focus

GlobalShortcuts portal in Plasma, GNOME and Hyprland; Sway and wlroots are left out

Capture and remote

XGetImage, RandR and x11vnc

PipeWire portal for OBS, wayvnc, KRDP and gnome-remote-desktop

Color and gamma

nvidia-settings and xrandr adjusted without formalities

Without an ICC profile there is no manual gamma adjustment in Plasma; the color protocol exists but does not measure the monitor

Automation

xdotool, xmodmap and AutoKey

One alternative per compositor with wtype or ydotool

Remote session

ssh -X

waypipe for Wayland apps; ssh -X only partially via XWayland

Two warnings prevent surprises. XWayland is not a security boundary: X11 applications in the same session share a single server and can still see each other. And these breakages are not a judgment on Wayland, but on who has migrated their code. KDE acknowledges much of the list in [its known issues wiki](https://community.kde.org/Plasma/Wayland_Known_Significant_Issues).

## Why does the answer depend on the compositor?

Wayland is a protocol, and as such it decides almost nothing of what the user sees. A compositor implements the portals, exposes extensions or not, and chooses its configuration format. Hence two machines with the same distribution have different experiences depending on the desktop.

In practice, GNOME and KDE are ahead with the reference implementations for shortcuts, capture, remote and input injection. The heart of the matter: on X11 any application could look at the keyboard and the pixels of the rest; on Wayland that is a request the user grants, not a right by default.

The push-to-talk case remains. Holding a key to talk does not quite fit the shortcuts portal, which notifies activation but not when the key is released. The usual, and ugly, workaround is to read events from /dev/input, which requires belonging to the input group.

## How to check your case in an afternoon?

The sensible way to decide is not to read comparisons, but to spend an afternoon with the Wayland session on your usual machine. Check which session you are in with \`echo $XDG\_SESSION\_TYPE\`: if it is already Wayland, your migration happened months ago and it is time to review what you left along the way.

Check the driver with \`nvidia-smi\` and \`glxinfo -B\`: community documentation places comfortable support from the 550 branch onward, while 470 and earlier do not support Wayland. Take inventory of X11 programs with \`xlsclients\`: that is the list you should review most carefully.

Test the tasks that break: share your screen on a video call, record with OBS using the PipeWire source, adjust the color of a monitor and trigger your most-used global shortcut. And have the way back ready: install a second session before changing your day-to-day one and keep a backup of \`~/.config\`.

Take inventory of X11 programs with \`xlsclients\`: that is the list you should review most carefully. Test the tasks that break: share your screen on a video call, record with OBS using the PipeWire source, adjust the color of a monitor and trigger your most-used global shortcut. And have the way back ready: install a second session before changing your day-to-day one and keep a backup of \`~/.config\`. Going back to X11 should cost a click, not a reinstall. The costly mistake is to assume the migration is transparent because the desktop starts, and to discover the gaps the day you have to present something in a meeting.

## What is still tied to X11 is not the desktop

After this week, staying on X11 no longer means staying on the usual desktop. It means choosing an LTS branch, a transitional desktop or an old driver, and accepting that you are moving away from main development. What there is not is a future version of Xorg with new features.

If your X11 session works and nothing fails, you do not have an emergency, you have a date. Set one, test it in time and migrate when your desktop stops offering it. Wayland no longer asks for blind trust, it asks for an afternoon of testing with your hardware in front of you.
