Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
(mention https://bugs.kde.org/show_bug.cgi?id=452219 (Worse performance on external monitor connected to NVIDIA GPU when default GPU is Intel))
 
(524 intermediate revisions by 34 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 quality-of-life annoyances, significant 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).


=== <s>No Drag and Drop between Wayland native and Xwayland clients</s> ===
<s>From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.</s>


'''Fixed''' in Plasma 5.16
== Session management ==
* 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.
* Session-restored XWayland windows go on the wrong screens and virtual desktops: https://bugs.kde.org/show_bug.cgi?id=468252 + https://bugs.kde.org/show_bug.cgi?id=421870


=== No remote support ===
== KWin/compositing/window management ==
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.
* 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
* Worse performance on weak Intel iGPUs: https://bugs.kde.org/show_bug.cgi?id=452119
* 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
* 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)
* Windows marked "Keep above other windows" cover up Meta+V Clipboard menu: https://bugs.kde.org/show_bug.cgi?id=462181
* Maximized XWayland windows have pixel gaps between screen edges when using a fractional scale factor: https://bugs.kde.org/show_bug.cgi?id=459373
* "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
* Fractional scaling below 100% breaks Chromium/Electron apps running in native Wayland mode: https://bugs.kde.org/show_bug.cgi?id=477676


'''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.
== Color Management ==
* 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
* 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


=== NVIDIA ===
== Accessibility ==
The NVIDIA blob is not supported as it uses a custom EGL extension. It would require additional code just for NVIDIA. On the other hand many users are on NVIDIA. Further information: [https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/ To EGL Stream or Not] and [https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/ Plasma/Wayland and NVIDIA – 2017 edition]
* Can't move pointer with numpad keys: https://bugs.kde.org/show_bug.cgi?id=478620
* Not all Sticky Keys options work: https://bugs.kde.org/show_bug.cgi?id=444335. Input on what is relevant/wanted there is welcome.


'''Partly fixed''' initial support was added in Plasma 5.16
== Graphics Tablet Support ==
 
* 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 pending [https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1972 Merge Request].
=== No Clipboard Manager protocol ===
* 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 clipboard history (e.g. Klipper and clipboard plasmoid) and no clipboard sync with KDE Connect.
* Can't assign mouse click presses to pen button as shortcuts, For example you want to change the default and assign a different button on a pen to do middle mouse click to pan the canvas in krita it won't accept middle mouse click as a shortcut- https://bugs.kde.org/show_bug.cgi?id=457636
 
* 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
'''In progress:''' https://phabricator.kde.org/T4449
* Can't calibrate tablets so there is no weird offset: https://bugs.kde.org/show_bug.cgi?id=476982 This is in the works and there is an open [https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1833 MR] by an awesome KDE contributor due for 6.1.
 
* 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.
== Input ==
* 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
=== No (wacom) Tablet support ===
* 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
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.
* 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
 
* The pointer for the graphic tablet is permanently a cross in plasma wayland. It doesn't change regardless of context. So if you want to resize a window with your pen, it will be troublesome to use this cursor, as it does not change to a resize handle cursor: https://bugs.kde.org/show_bug.cgi?id=477570.
=== No configurable gestures ===
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 ===
We lack a functionality like XModmap to remap keys. See [https://github.com/xkbcommon/libxkbcommon/issues/40 xkbcommon-issue40] --> Explain how this issue is related?


== Plasma ==
== Plasma ==
=== <s>Virtual Desktops</s> ===
* XWayland applications may not autostart properly in a Wayland session due to various important environment variables not being set: https://bugs.kde.org/show_bug.cgi?id=469839
<s>We don't have an API yet for virtual desktops, so pager is not working</s>
* XEmbedSNIProxy window eats input in top-left pixel of the screen: https://bugs.kde.org/show_bug.cgi?id=433079
 
* Global Menu is not supported for non-Qt apps: https://bugs.kde.org/show_bug.cgi?id=424485
'''Fixed''' in Plasma 5.15
* Installed Chrome apps are grouped together with Chrome windows in Icon-Only Task Manager: https://bugs.kde.org/show_bug.cgi?id=358277
 
* Plasma quits (doesn't crash) when too many windows are open: https://bugs.kde.org/show_bug.cgi?id=479492
=== Native Wayland windows are not restored ===
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 ===
We don't have an API yet for window thumbnails.
 
=== No window move on empty area in breeze ===
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.
 
=== <s>Logout</s> ===
<s>[https://bugs.kde.org/show_bug.cgi?id=372789 There's a crash I know] (but fixing properly breaks X). [https://github.com/sddm/sddm/issues/897 Might be more stuff with SDDM], needs investigation</s>
 
'''Fixed''' in Plasma 5.16.3
 
=== No activities ===
Activities are probably not a must-have feature, but anyway this is annoying for those who got accustomed to them on X11.
 
== Qt ==
=== <s>No animated cursors</s> ===
<s>See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]</s>
 
'''Fixed''' in Qt 5.14


=== <s>Key repeat not working</s> ===
== NVIDIA ==
<s>See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]</s>
* Transient graphical glitches after waking from sleep: https://bugs.kde.org/show_bug.cgi?id=448866
* Transient graphical glitches after changing themes: https://bugs.kde.org/show_bug.cgi?id=470503


'''Fixed''' in Qt 5.13
== Upstream ==


=== No tablet support ===
=== Not yet started ===
QtWayland does not yet support the tablet API. So even if KWin had support, Qt would not be able to use it.
* 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 instability or unresponsiveness: https://gitlab.freedesktop.org/wayland/wayland/-/issues/443


=== <s>Fullscreen does not work</s> ===
=== Work in progress ===
<s>see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]</s>
* With NVIDIA GPU, Plasma popups (e.g. Kickoff and KRunner) sometimes stops showing after opening / closing them a few times: https://bugs.kde.org/show_bug.cgi?id=455913 / https://codereview.qt-project.org/c/qt/qtwayland/+/503674 (Fixed in KWin for Qt <= 6.6.2, Fixed in Qt 6.6.3)
* 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)
* When dragging files, to trigger a specific result, you have to hold down a modifier key *before* you start dragging, not after: https://bugs.kde.org/show_bug.cgi?id=423031 - https://codereview.qt-project.org/c/qt/qtwayland/+/525413 (Not yet merged)
* 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)


'''Fixed''' in Qt 5.12
=== Fixed in an upcoming version ===
* When dragging images from Firefox to the desktop, have to hold the drag 1 or more seconds over the desktop before releasing or else the desktop drop menu does not appear: https://bugs.kde.org/show_bug.cgi?id=448867 - Fixed in Qt 6.7
* Quick tile actions and window rules cannot override window's minimum size if needed as they can on X11: https://bugs.kde.org/show_bug.cgi?id=434615 - Fixed in Qt 6.7
* Dialog Parent effect isn't working: https://bugs.kde.org/show_bug.cgi?id=460819 – fixed in Qt 6.8 and KWin 6.1
* Creative applications often use single modifier shortcuts. Artists can map these keys to their pen buttons; for example, holding ctrl to colour pick while painting: https://bugs.kde.org/show_bug.cgi?id=461259 - Fixed for 6.1

Latest revision as of 14:53, 9 April 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.


Session management

KWin/compositing/window management

Color Management

  • 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
  • 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

Accessibility

Graphics Tablet Support

  • 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 pending Merge Request.
  • Can't switch between absolute and relative modes for the graphic tablet. Bug report and Pending Merge Requests 1 and 2.
  • Can't assign mouse click presses to pen button as shortcuts, For example you want to change the default and assign a different button on a pen to do middle mouse click to pan the canvas in krita it won't accept middle mouse click as a shortcut- https://bugs.kde.org/show_bug.cgi?id=457636
  • 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 calibrate tablets so there is no weird offset: https://bugs.kde.org/show_bug.cgi?id=476982 This is in the works and there is an open MR by an awesome KDE contributor due for 6.1.
  • 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
  • The pointer for the graphic tablet is permanently a cross in plasma wayland. It doesn't change regardless of context. So if you want to resize a window with your pen, it will be troublesome to use this cursor, as it does not change to a resize handle cursor: https://bugs.kde.org/show_bug.cgi?id=477570.

Plasma

NVIDIA

Upstream

Not yet started

Work in progress

Fixed in an upcoming version

Retrieved from "https://community.kde.org/index.php?title=Plasma/Wayland_Known_Significant_Issues&oldid=100552"