Plasma 6: moving from X11 habits to Wayland

Source and license: This article includes an edited adaptation of “My Early Experiences with KDE Plasma 6” by Zhanfeng Qianxue (Fengxuecheng). The original and the portions of this article adapted from it are provided under CC BY-NC-SA 4.0, which requires attribution, noncommercial use, and sharing under the same license. This article selects and rewords material from the original and adds version and verification boundaries; the original author's personal experiences remain their own. This license notice was added on 2026-10-09. It applies only to the source material identified above and its adaptations, does not extend that license to other content on this site, and does not imply the original author's endorsement of this site.

This is an edited clipping with explicit version boundaries, sourced from a technical article on Fengxuecheng. It preserves the configuration approaches and tool references, while historical bugs and workarounds serve only to explain the environment at the time, rather than as general installation advice today. All first-person experiences below refer to the original author; this site has not reproduced these failures.

Wayland#

KDE 6 switched its default graphical environment to Wayland. Wayland's underlying design differs considerably from X11, and its permission controls are strict.
Here is a brief list of differences I can think of that require manual changes:
🆎 The way Fcitx 5 is enabled has changed. There is no longer a need to set numerous environment variables; only XMODIFIERS is needed. See the Fcitx 5 Wiki for the specific configuration.
Note, however, that this setup does not enable input methods in some proprietary X11 applications running under XWayland, such as WPS Office and some Wine applications. Set environment variables such as QT_IM_MODULE separately for those applications.
🔧 The Wayland protocol itself does not read shell configuration. Whether .xprofile is loaded depends on the session startup chain; environment.d is intended for systemd user services and does not immediately affect every process already running. First establish which layer imports the variables, then choose an entry point supported by that session.
🔧 Many window-management utilities, including xprop, xdotool, and wmctrl, are no longer usable for this purpose. Use KWin's built-in scripting support instead. If needed, scripts can also communicate with external programs through DBus.
For KWin scripting, see the documentation below:
📹 Screenshots and screen recording work differently. Mainstream screenshot tools such as Spectacle and Flameshot, and recording tools such as OBS Studio, already support Wayland. However, KDE's KColorChooser screen color picker still did not work correctly in the version discussed here; a screenshot tool's color picker can serve as a workaround.

Qt 6 and Theme Changes#

KDE 6 is built on Qt 6, so theme tools such as Kvantum also need to be replaced with their Qt 6 versions.
The kvantum package in the official Arch Linux repositories removed all background blur effects in the original author's setup at the time. The author installed the AUR packages kvantum-git and kvantum-qt5-git; with both installed, themes worked correctly in Qt 6 and Qt 5 applications.
KDE 6 also substantially changed how it handles third-party icon themes. For example, Plasma Shell no longer reads icons from Plasma themes, which may explain misbehaving system-tray icons. If the icon theme's developer has not updated it in time, you will need to adapt it yourself using this KDE developer's blog post as a reference.

File Pickers#

✳️ Qt6 and XDG Desktop Portal
If file pickers in Qt 6 applications are extremely slow, the following configuration file can address the problem:
~/.config/systemd/user/plasma-xdg-desktop-portal-kde.service.d/override.conf

[Service]
Environment="QT_QPA_PLATFORMTHEME=KDE"

This is the original article's service-override example for Plasma 6.0.4. Verify the actual unit name and current environment before using it; save relevant work first, then load the configuration through the user-service management procedure. Do not apply a historical workaround unconditionally to every environment.

🪃 Note: If you previously followed my KDE 5 article and configured the QT_QPA_PLATFORMTHEME variable and the /usr/bin/killall xdg-desktop-portal-kde startup script, I am sorry to say that this configuration caused a serious problem in KDE 6. Both settings need to be removed.
👣 GNOME / GTK
Under Wayland, GTK_USE_PORTAL can still make GTK use the XDG Desktop Portal file picker, but enabling it makes the mouse pointer revert to the default theme and become extremely large. At the time of writing, apart from Firefox, which provides a configuration option, most GTK / Electron applications had to use the GTK file picker.

Rounded Window Corners and Background Blur#

The rounded-corner plugin LightlyShaders still works with KDE 6; compile and install its plasma6 branch.
In KDE 5, applying blur to windows such as Alacritty that do not support KDE's blur effect themselves required the Force Blur script. Scripts based on xprop cannot control native Wayland windows. One solution is to install kwin-effects-forceblur, which modifies KDE's built-in Blur effect to force background blur on specified windows.
After installing kwin-effects-forceblur, you must disable KDE's built-in Blur and LightlyShaders' Blur (LightlyShaders) effects.

Restarting the Desktop#

Something in KDE 6 may still have been leaking memory, potentially causing severe sluggishness after extended use. Under Wayland, however, the window manager and compositor are integrated, and restarting the window manager was reported to kill non-Qt 6 applications.
The original article relayed that major frameworks were actively adapting, but at the time only Qt 6 handled this well enough to avoid being killed.
The original article recorded qdbus org.kde.KWin /KWin replace. Under Wayland, a compositor exit may disconnect clients and lose unsaved work; there is no guarantee that all Qt6 applications survive. For routine recovery, prefer saving your work and logging out normally. The command is retained here as a historical interface reference, not as a safe, lossless shortcut.

Dark Mode#

With the built-in Breeze theme, dark mode works particularly well in KDE 6.
For third-party themes, use Yin-Yang to switch dark mode, or write your own script using the original author's implementation as a reference.

Touchpad Gestures#

KDE 6 hardcodes several touchpad gestures that cannot normally be changed.
You can build and install KWin with the original author's kwin-without-gestures patch to disable KDE's built-in gestures, then configure your own using tools such as libinput-gestures or touchegg. The choice of tool comes down to which feels right for your habits.
touchegg supports different gestures for different applications under X11, but not under Wayland. You can write a program yourself, for example using the original author's implementation as a reference.

Dock and Widgets#

Latte Dock cannot be used with KDE 6. With some configuration, however, KDE 6's panels can provide an experience similar to Latte Dock.
Install this widget to customize the panel.
When the original article was written, KDE 6's widget ecosystem was still limited, and many established widgets had not been ported. To preserve the existing desktop layout and usage habits, the original author learned how to write several widgets.
The original author hoped KDE 6 would eventually develop a thriving widget ecosystem like KDE 5's.

The Original Author's Screenshots#