Jump to content

Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
Davidedmundson (talk | contribs)
Ngraham (talk | contribs)
Session restore is now implemented for Plasma 6.4!
 
(587 intermediate revisions by 35 users not shown)
Line 1: Line 1:
This page tracks the Wayland showstoppers through out the stack
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]].


== General issues ==
It is the Wayland-specific companion to [[Plasma/X11 Known Significant Issues]].
=== No vertical / horizontal maximize of Wayland native clients ===
KWin uses NetWM modes internally to do this. Works with Xwayland clients. Would also work for Wayland clients, just the state cannot be exported to Wayland (c.f. Quick tiling).


=== No remote support ===
Note that to actually ''drop'' X11 support, even more is needed; see https://invent.kde.org/plasma/kwin/-/issues/202.
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.


'''Partly fixed''' since we now have an API for screencast using a separate KWayland interface. There is also already support in xdg-desktop-portals for convenience of other apps and general support in Flatpaks. What's still missing is an API for remote input.


=== NVIDIA ===
== KWin/compositing/window management ==
The NVIDIA blob uses a custom EGL extension which [https://phabricator.kde.org/D18570 Plasma 5.16 added support] for. It requires setting the ''KWIN_DRM_USE_EGL_STREAMS=1'' environment variable to activate.
* 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 [https://invent.kde.org/plasma/kwin/-/merge_requests/3362 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. [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 - in progress with https://invent.kde.org/plasma/kwin/-/merge_requests/7348
* 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
 


Other aspects of the "Wayland experience" with NVIDIA such as XWayland compatibility are outside of our influence.
== KDE applications ==
* Cross-app activation/window raising doesn't work for certain apps and use cases:
** Opening files using command-line binaries in Konsole: https://bugs.kde.org/show_bug.cgi?id=442265
** Opening files from KRunner: https://bugs.kde.org/show_bug.cgi?id=475706
** Opening the Trash from a widget when Dolphin is already running: https://bugs.kde.org/show_bug.cgi?id=499936


'''Partly fixed:''' Requires manual activation.


=== No Clipboard Manager protocol ===
== Upstream ==
No clipboard history (e.g. Klipper and clipboard plasmoid) and no clipboard sync with KDE Connect.


'''In progress:''' https://phabricator.kde.org/T4449
=== Waiting on new Wayland protocol ===
* 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 [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
* 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


== Input ==
=== Qt ===
=== No configurable gestures ===
* Sub-menus are mis-positioned when parent menu is close to a screen edge: https://bugs.kde.org/show_bug.cgi?id=500584 / https://bugreports.qt.io/browse/QTBUG-124810 + https://bugreports.qt.io/browse/QTBUG-99618
X has the ability to accept fake input events to allow programs such as Easystroke. With the new security model of Wayland, such a program would need to be part of the compositor.


=== No XModmap ===
=== GTK ===
We lack a functionality like XModmap to remap keys.
* 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


== Plasma ==
=== GStreamer ===
=== Native Wayland windows are not restored ===
* GStreamer with OpenGL creates an empty "OpenGL Renderer" window on Wayland: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2997
Session restoring does not include Wayland native windows. 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 GNOME has according to [https://wiki.gnome.org/Projects/SessionManagement/GnomeSession their wiki] an own implementation for some time.


=== No window thumbnails ===
=== NVIDIA ===
We don't have an API yet for window thumbnails.
* Worse performance on external monitor connected to NVIDIA GPU when default GPU is Intel: https://bugs.kde.org/show_bug.cgi?id=452219


=== No window move on empty area in breeze ===
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.


=== No activities ===
== Fixed in an upcoming version ==
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.
* No session restore for native Wayland windows: https://bugs.kde.org/show_bug.cgi?id=436318 / https://invent.kde.org/plasma/kwin/-/issues/113. Preliminary support is implemented in Plasma 6.4, and toolkits and apps will need to opt into supporting it.

Latest revision as of 16:42, 10 April 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.

Note that to actually drop X11 support, even more is needed; see https://invent.kde.org/plasma/kwin/-/issues/202.


KWin/compositing/window management


Accessibility


Graphics Tablet Support


KDE applications


Upstream

Waiting on new Wayland protocol

Qt

GTK

GStreamer

NVIDIA


Fixed in an upcoming version