Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
(Add https://bugs.kde.org/show_bug.cgi?id=428706 (Cannot unlock session after external screen turns off))
(Mention the virtual keyboard situation)
 
(466 intermediate revisions by 32 users not shown)
Line 1: Line 1:
This page tracks the Wayland showstoppers throughout the stack. 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 quality-of-life annoyances, significant 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]].
 


== KWin/compositing/window management ==
== KWin/compositing/window management ==
* When the compositor crashes, all apps crash too: https://bugreports.qt.io/browse/QTBUG-85631
* Worse performance on external monitor connected to NVIDIA GPU when default GPU is Intel: https://bugs.kde.org/show_bug.cgi?id=452219
* 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
* With NVIDIA GPU, transient graphical glitches after changing themes: https://bugs.kde.org/show_bug.cgi?id=470503
 
== Accessibility ==
* Can't move pointer with numpad keys: https://bugs.kde.org/show_bug.cgi?id=478620
* 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)


* No Wayland protocol for cross-app window activation/focus, or launch feedback: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/50
== Graphics Tablet Support ==
** Windows don't get brought forward when activated by another app: https://bugs.kde.org/show_bug.cgi?id=424795
* 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].
** No feedback on the Task Manager when an app is launched: https://bugs.kde.org/show_bug.cgi?id=402903
* 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
** No feedback on the cursor when an app is launched: https://bugs.kde.org/show_bug.cgi?id=405624
* Can't map a portion of the tablet area to the screen. Some people have large tablet and sometime they want to map a portion of the tablet to the monitor: https://bugs.kde.org/show_bug.cgi?id=457703.
* Secondary screen doesn't come back on after disconnecting and reconnecting: https://bugs.kde.org/show_bug.cgi?id=434683
* 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
* "Pin/keep open" functionality for Plasma applets does not work: https://bugs.kde.org/show_bug.cgi?id=400317
* 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
* Very blurry fractional scaling for native Wayland windows due to using a downsampled 2x or 3x pixmap: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/34
* 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
* Some menus appear in the wrong location as separate windows with titlebars:
** Context menus: https://bugs.kde.org/show_bug.cgi?id=417378
** In-titlebar app menu: https://bugs.kde.org/show_bug.cgi?id=430662


== Upstream ==


== Input ==
=== Waiting on new Wayland protocol ===
* Touchpad Gestures:
* No session restore for native Wayland windows: https://bugs.kde.org/show_bug.cgi?id=436318. 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.
** They are not configurable: https://bugs.kde.org/show_bug.cgi?id=402857
* 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)
** They are very boolean, they don't show any feedback until they're executed.
* Graphics programs that require color accuracy in professional settings such as Krita, GIMP, Scribus, Darktable, Blender, DaVinci Resolve, etc. cannot guarantee accuracy, especially when moving between color spaces like sRGB and CMYK (from digital to print) or Rec. 709 (broadcast TV) until the Color Management and HDR protocol is merged and compositors like KWin implement support for it: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14
* Can't type accented characters in native Wayland Qt apps: https://bugs.kde.org/show_bug.cgi?id=411729 / https://bugreports.qt.io/browse/QTBUG-87088
* 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


=== Not yet started ===
* 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.
* With a high DPI mouse, some applications might experience unresponsiveness: https://bugs.kde.org/show_bug.cgi?id=450139


== Plasma ==
=== Work in progress ===
* 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.
* 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
* No activities. KWin now has minimal support for them, but the Task Manager doesn't know how to interact with them yet, and it's not properly persisted, so it doesn't survive session restarts. https://invent.kde.org/plasma/kwin/-/merge_requests/753
* When using a Chromium-based browser in native Wayland mode, dragging an image to the desktop creates a sticky note out of it: https://bugs.kde.org/show_bug.cgi?id=449645 / https://codereview.qt-project.org/c/qt/qtwayland/+/518017 (Fixed in Qt 6.6) + https://codereview.qt-project.org/c/qt/qtwayland/+/518018 (Not yet merged)
* Context menus close immediately when the tooltip for thing that you right-clicked on closes itself: https://bugs.kde.org/show_bug.cgi?id=417939
* QtQuick windows exhibit jittery resizing: https://bugs.kde.org/show_bug.cgi?id=477900 - https://codereview.qt-project.org/c/qt/qtwayland/+/503676 (Work in progress)
* Text copied from a GTK app makes it into Klipper, but cannot be pasted after the GTK app quits: https://bugs.kde.org/show_bug.cgi?id=424649
* System Settings sometimes crashes when changing Global Themes: https://bugs.kde.org/show_bug.cgi?id=435009
* Cannot unlock session after external screen turns off: https://bugs.kde.org/show_bug.cgi?id=428706


== Drag and Drop issues ==
=== Fixed in an upcoming version ===
* Plasma crashes when dragging a file over the panel: https://bugs.kde.org/show_bug.cgi?id=398440
* Can't fine tune pressure curve of the tablet. Various people draw with varying pressure; some people draw with heavy hand some use light touch. Configuring pressure curve helps artists to get better lines. [https://bugs.kde.org/show_bug.cgi?id=457705 Bug report] and [https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1972 Merge Request]. - Implemented in Plasma 6.3.0
* 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

Latest revision as of 19:07, 27 November 2024

This page tracks the "Errata/Known issues" that are specific to the the Plasma Wayland session: significant quality-of-life annoyances, significant 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

Accessibility

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
  • Can't map a portion of the tablet area to the screen. Some people have large tablet and sometime they want to map a portion of the tablet to the monitor: https://bugs.kde.org/show_bug.cgi?id=457703.
  • 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

Not yet started

Work in progress

Fixed in an upcoming version

  • Can't fine tune pressure curve of the tablet. Various people draw with varying pressure; some people draw with heavy hand some use light touch. Configuring pressure curve helps artists to get better lines. Bug report and Merge Request. - Implemented in Plasma 6.3.0