Plasma/Wayland Known Significant Issues: Difference between revisions

Latest revision as of 11:46, 12 February 2025

This page tracks the "Errata/Known issues" that are specific to the the Plasma Wayland session: significant omissions compared to the X11 session, quality-of-life annoyances, problems with workarounds, etc. This is part of KDE's Wayland goal.

It is the Wayland-specific companion to Plasma/X11 Known Significant Issues.

KWin/compositing/window management

Native Wayland windows cannot save and restore their window positions; KWin would need to do it: https://bugs.kde.org/show_bug.cgi?id=15329
"Spare Layouts" feature not implemented: https://bugs.kde.org/show_bug.cgi?id=455431
Using key combination shortcuts to type phrases into windows is not yet implemented: https://bugs.kde.org/show_bug.cgi?id=478219
No way to change the gamma or manually adjust the colors without generating or finding an appropriate ICC profile

Accessibility

Can't move pointer with numpad keys: https://bugs.kde.org/show_bug.cgi?id=478620 - there's a pending Merge request
Slow Keys feature doesn't work: https://bugs.kde.org/show_bug.cgi?id=490826
Only Maliit is supported, which is not a proper accessibility-oriented virtual keyboard (e.g. no modifier keys or arrow keys)

Graphics Tablet Support

Can't switch between absolute and relative modes for the graphic tablet. Bug report and Pending Merge Requests 1 and 2.
Can't create multiple profiles for tablet configurations so artists can choose different profiles (e.g. different shortcuts and pen pressure) for different workflows like inking a comic or doing vector art: https://bugs.kde.org/show_bug.cgi?id=477671
The UI for mapping tablet area and its buttons has a few issues compared to the UI in the X11 KCM: https://bugs.kde.org/show_bug.cgi?id=477750
Graphic tablets may have a touch strip or ring, but in the Wayland KCM, you can't assign shortcuts to touch rings. Bug report: https://bugs.kde.org/show_bug.cgi?id=477752
Some tablets allow users to switch between touch ring modes. For example, you can click a button and change the mode from one set of shortcuts like scrolling to another set of shortcuts, like changing hue or zooming in and out. This is not possible on Plasma Wayland: https://bugs.kde.org/show_bug.cgi?id=477787

Upstream

Waiting on new Wayland protocol

No session restore for native Wayland windows: https://bugs.kde.org/show_bug.cgi?id=436318 / https://invent.kde.org/plasma/kwin/-/issues/113. Our session management recovery engine is based on the X Session Management Protocol and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and GNOME has had their own implementation for some time. Possible workaround: Use Hibernation (Suspend To Disk) instead.
Picture-in-Picture windows from web browsers get a Task Manager icon and do not stay on top: https://bugs.kde.org/show_bug.cgi?id=463288; requires https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/132 and adoption in apps using PiP windows (like web browsers)
Calibration/Profiling tools like DisplayCAL and argyllcms are used with colorimeters to ensure monitors are displaying color accurately. A portal (which has not been proposed yet) is required for these tools to be able to calibrate the monitor on Wayland and hand the ICC profile over to the compositor as discussed here. Relevant DisplayCAL issue here: https://github.com/eoyilmaz/displaycal-py3/issues/133
Global Menu is not supported for non-Qt apps: https://bugs.kde.org/show_bug.cgi?id=424485. Needed wayland protocol: see https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/52

GTK

With screen scaling, cursor size is incorrect when hovering over native Wayland apps written with the GTK toolkit due to its lack of support for the cursor-shape-v1 protocol: https://bugs.kde.org/show_bug.cgi?id=451158. See also https://bugs.kde.org/show_bug.cgi?id=459161 for general cursor size issues.
When the compositor crashes or restarts, non-Qt apps are killed — Qt apps do stay alive, and work is ongoing to make other apps survive as well; see see https://invent.kde.org/plasma/kwin/-/wikis/Restarting

NVIDIA

Worse performance on external monitor connected to NVIDIA GPU when default GPU is Intel: https://bugs.kde.org/show_bug.cgi?id=452219

Fixed in an upcoming version

QtQuick windows exhibit jittery resizing: https://bugs.kde.org/show_bug.cgi?id=477900 - https://codereview.qt-project.org/c/qt/qtwayland/+/591892 - Fixed in Qt 6.9.0

@@ Line 1: / Line 1: @@
-This page tracks the Wayland showstoppers throughout the stack. Showstoppers are major bugs, or missing features affecting the Wayland session but not the X11 session. This is part of KDE's [[Goals/Wayland|Wayland goal]].
+This page tracks the "Errata/Known issues" that are specific to the the Plasma Wayland session: significant omissions compared to the X11 session, quality-of-life annoyances, problems with workarounds, etc. This is part of KDE's [[Goals/Wayland|Wayland goal]].
+It is the Wayland-specific companion to [[Plasma/X11 Known Significant Issues]].
-== Login/Session management ==
-* Session restoring does not include Wayland native windows: https://bugs.kde.org/show_bug.cgi?id=436318. Our sessions management recover engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession GNOME has had their own implementation] for some time.
-* Windows that *are* session-restored go on the wrong virtual desktops: https://bugs.kde.org/show_bug.cgi?id=421870
-* After kwin_wayland crashes and/or restarts, logout screen/actions stops working: https://bugs.kde.org/show_bug.cgi?id=449948
 == KWin/compositing/window management ==
-* When the compositor crashes or restarts, all apps are killed
+* Native Wayland windows cannot save and restore their window positions; KWin would need to do it: https://bugs.kde.org/show_bug.cgi?id=15329
-* Windows that were closed when maximized will open in the maximized position, but not the maximized state: https://bugs.kde.org/show_bug.cgi?id=437089
+* "Spare Layouts" feature not implemented: https://bugs.kde.org/show_bug.cgi?id=455431
-* On Wayland, the compositor doesn't expose the minimized state. Some application and library code currently does things based on that state (usually to show their window again if needed, typically by calling QWidget::isMinimized()). Example: KNotifications' KStatusNotifierItem in KStatusNotifierItemPrivate::checkVisibility(...), invoked e.g. on clicking the item, uses the info to decide client-side whether to request showing the window again (or hide it)
+* Using key combination shortcuts to type phrases into windows is not yet implemented: https://bugs.kde.org/show_bug.cgi?id=478219
+* No way to change the gamma or manually adjust the colors without generating or finding an appropriate ICC profile
-== Plasma ==
-* Saving and restoring activities does not work
-* Monitor connector names are different across X11 and Wayland, so logging into a Wayland session from X11 breaks multimonitor layout and Plasma configs: https://bugs.kde.org/show_bug.cgi?id=385135
-* XEmbedSNIProxy window eats input in top-left pixel of the screen: https://bugs.kde.org/show_bug.cgi?id=433079
-* XWayland-using Chromium web apps show the wrong icon: https://bugs.kde.org/show_bug.cgi?id=447845
-* When using scaling, scale is reset and re-applied on login, causing various issues: https://bugs.kde.org/show_bug.cgi?id=449212
-* Some apps don't appear in Task Manager: https://bugs.kde.org/show_bug.cgi?id=444325
-== System Settings ==
+== Accessibility ==
-* Gamma KCM doesn't work/isn't visible
+* Can't move pointer with numpad keys: https://bugs.kde.org/show_bug.cgi?id=478620 - there's a [https://invent.kde.org/plasma/kwin/-/merge_requests/3362 pending Merge request]
-* Graphic tablet KCM is very barebones compared to X11 version: https://bugs.kde.org/show_bug.cgi?id=433045
+* Slow Keys feature doesn't work: https://bugs.kde.org/show_bug.cgi?id=490826
+* Only Maliit is supported, which is not a proper accessibility-oriented virtual keyboard (e.g. no modifier keys or arrow keys)
-== Drag and Drop issues ==
+== Graphics Tablet Support ==
-* Can't abort drag-and-drop with the Esc key while dropped file is over Plasma panel or desktop: https://bugs.kde.org/show_bug.cgi?id=405267
+* Can't switch between absolute and relative modes for the graphic tablet. [https://bugs.kde.org/show_bug.cgi?id=477898 Bug report] and Pending Merge Requests [https://invent.kde.org/plasma/kwin/-/merge_requests/4852 1] and [https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1963 2].
+* Can't create multiple profiles for tablet configurations so artists can choose different profiles (e.g. different shortcuts and pen pressure) for different workflows like inking a comic or doing vector art: https://bugs.kde.org/show_bug.cgi?id=477671
+* The UI for mapping tablet area and its buttons has a few issues compared to the UI in the X11 KCM: https://bugs.kde.org/show_bug.cgi?id=477750
+* Graphic tablets may have a touch strip or ring, but in the Wayland KCM, you can't assign shortcuts to touch rings. Bug report: https://bugs.kde.org/show_bug.cgi?id=477752
+* Some tablets allow users to switch between touch ring modes. For example, you can click a button and change the mode from one set of shortcuts like scrolling to another set of shortcuts, like changing hue or zooming in and out. This is not possible on Plasma Wayland: https://bugs.kde.org/show_bug.cgi?id=477787
-== Blocked on required upstream changes ==
-* When using any scale factor above 100%, XWayland apps are blurry from being upscaled from the 100% version: https://bugs.kde.org/show_bug.cgi?id=446674; requires https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/733
+== Upstream ==
-* When using a fractional scale factor, native Wayland apps are slightly blurry: https://bugs.kde.org/show_bug.cgi?id=446674; requires  https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/34
-* No color management: https://bugs.kde.org/show_bug.cgi?id=439135; requires https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14
+=== Waiting on new Wayland protocol ===
-* KDE app windows don't get brought forward when activated by another KDE app: requires Qt6; support was added in https://codereview.qt-project.org/c/qt/qtwayland/+/321246
+* No session restore for native Wayland windows: https://bugs.kde.org/show_bug.cgi?id=436318 / https://invent.kde.org/plasma/kwin/-/issues/113. Our session management recovery engine is based on the [https://www.x.org/releases/X11R7.7/doc/libSM/xsmp.html X Session Management Protocol] and there is apparently currently no generic concept to do it on Wayland. But on Qt it's plugin-able and [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession GNOME has had their own implementation] for some time. Possible workaround: Use Hibernation (Suspend To Disk) instead.
-* KDE app windows activated by Electron apps don't get brought forward due to lack of support for the Activation protocol in the toolkit: https://github.com/electron/electron/issues/30912
+* Picture-in-Picture windows from web browsers get a Task Manager icon and do not stay on top: https://bugs.kde.org/show_bug.cgi?id=463288; requires https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/132 and adoption in apps using PiP windows (like web browsers)
-* Picture-in-Picture windows from web browsers do not stay on top: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/44
+* Calibration/Profiling tools like DisplayCAL and argyllcms are used with [https://en.wikipedia.org/wiki/Tristimulus_colorimeter colorimeters] to ensure monitors are displaying color accurately. A portal (which has not been proposed yet) is required for these tools to be able to calibrate the monitor on Wayland and hand the ICC profile over to the compositor as discussed [https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14#note_2125072 here]. Relevant DisplayCAL issue here: https://github.com/eoyilmaz/displaycal-py3/issues/133
-* When a notification times out, it closes any context menus that are open and then blocks the next two right-clicks: https://bugs.kde.org/show_bug.cgi?id=427542; requires https://codereview.qt-project.org/c/qt/qtwayland/+/347783
+* Global Menu is not supported for non-Qt apps: https://bugs.kde.org/show_bug.cgi?id=424485. Needed wayland protocol: see https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/52
-* Installed Chrome apps do not show up as a unique app but instead assume the Chrome icon, in Icon-Only Task Manager: https://bugs.kde.org/show_bug.cgi?id=358277
-* Wrong positioning of context menu in multiple screens: https://bugs.kde.org/show_bug.cgi?id=436016; requires https://bugreports.qt.io/browse/QTBUG-85297
+=== GTK ===
+* With screen scaling, cursor size is incorrect when hovering over native Wayland apps written with the GTK toolkit due to its lack of support for the cursor-shape-v1 protocol: https://bugs.kde.org/show_bug.cgi?id=451158. See also https://bugs.kde.org/show_bug.cgi?id=459161 for general cursor size issues.
+* When the compositor crashes or restarts, non-Qt apps are killed — Qt apps do stay alive, and work is ongoing to make other apps survive as well; see see https://invent.kde.org/plasma/kwin/-/wikis/Restarting
+=== NVIDIA ===
+* Worse performance on external monitor connected to NVIDIA GPU when default GPU is Intel: https://bugs.kde.org/show_bug.cgi?id=452219
+== Fixed in an upcoming version ==
+* QtQuick windows exhibit jittery resizing: https://bugs.kde.org/show_bug.cgi?id=477900 - https://codereview.qt-project.org/c/qt/qtwayland/+/591892 - Fixed in Qt 6.9.0