Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
(Use bullet points)
(Move compositor restart issue into the Upstream section since all the remaining work needs to be done in other toolkits)
 
(516 intermediate revisions by 34 users not shown)
Line 1: Line 1:
This page tracks the Wayland showstoppers throughout 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]].
 
It is the Wayland-specific companion to [[Plasma/X11 Known Significant Issues]].




== KWin/compositing/window management ==
== KWin/compositing/window management ==
* No cross-app window activation/focus protocol. As a result, windows don't get brought forward when activated by another app: https://bugs.kde.org/show_bug.cgi?id=424795
* Worse performance on external monitor connected to NVIDIA GPU when default GPU is Intel: https://bugs.kde.org/show_bug.cgi?id=452219
* 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).
* 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
* Task Switchers become black and unusable after switching: https://bugs.kde.org/show_bug.cgi?id=415798
* Maximized XWayland windows have pixel gaps between screen edges when using a fractional scale factor: https://bugs.kde.org/show_bug.cgi?id=459373
* XWayland windows are upscaled and look blurry and ugly in HiDPI mode: https://bugs.kde.org/show_bug.cgi?id=389191
* "Spare Layouts" feature not implemented: https://bugs.kde.org/show_bug.cgi?id=455431
* Cursor lags under high CPU load: https://bugs.kde.org/show_bug.cgi?id=421131
* Using key combination shortcuts to type phrases into windows is not yet implemented: https://bugs.kde.org/show_bug.cgi?id=478219
* KDE app windows don't remember maximized state: https://bugs.kde.org/show_bug.cgi?id=409919
* Can't dismiss a popup by clicking another window of the same application: https://bugreports.qt.io/browse/QTBUG-83972


== Accessibility ==
* 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.


== Remote control support incomplete ==
== Graphics Tablet Support ==
* Our screencasting API handles remote video streaming, but there is no API for remote input, so things like TeamViewer have no way to work (and would need to be ported to use those APIs once they exist).
* 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].
* 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 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 [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.
* 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 ==
* 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
* Installed Chrome apps are grouped together with Chrome windows in Icon-Only Task Manager: https://bugs.kde.org/show_bug.cgi?id=358277


== NVIDIA ==
== NVIDIA ==
'''Partly fixed:''' Requires manual activation.
* 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


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. Other aspects of the "Wayland experience" with NVIDIA such as XWayland compatibility are outside of our influence.
== Upstream ==


=== Waiting on new Wayland protocol ===
* 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.
* 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)
* 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
* 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 ==
=== Not yet started ===
* No configurable mouse 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.
* 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.
* No XModmap; we lack a functionality like XModmap to remap keys.
* With a high DPI mouse, some applications might experience instability or unresponsiveness: https://gitlab.freedesktop.org/wayland/wayland/-/issues/443
 
 
== Plasma ==
* 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 move on empty area in breeze; This broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.
* No activities.
* Keyboard Layout indicator system tray item doesn't work: https://bugs.kde.org/show_bug.cgi?id=390079


== Drag and Drop issues ==
=== Work in progress ===
* 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
* 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)
* 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)


* Dragging-and-dropping a file to https://imgur.com in Firefox brings down the whole session: https://bugs.kde.org/show_bug.cgi?id=421130
=== Fixed in an upcoming version ===
* Drag and drop on Wayland: Wrong drop destination on drag'n drop https://bugs.kde.org/show_bug.cgi?id=422414
* Dialog Parent effect isn't working: https://bugs.kde.org/show_bug.cgi?id=460819 – Fixed in Plasma 6.1 and Qt 6.8
* https://bugs.kde.org/show_bug.cgi?id=390321
* 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 - Fixed in Qt 6.8
* https://bugs.kde.org/show_bug.cgi?id=400014
* https://bugs.kde.org/show_bug.cgi?id=383794
* https://bugs.kde.org/show_bug.cgi?id=405267
* https://bugs.kde.org/show_bug.cgi?id=389261
* https://bugs.kde.org/show_bug.cgi?id=398440
* https://bugs.kde.org/show_bug.cgi?id=418683
* https://bugs.kde.org/show_bug.cgi?id=420949
* https://bugs.kde.org/show_bug.cgi?id=414834
* https://bugs.kde.org/show_bug.cgi?id=419017

Latest revision as of 00:06, 8 June 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 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

Waiting on new Wayland protocol

Not yet started

Work in progress

Fixed in an upcoming version