Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
No edit summary
(https://bugs.kde.org/show_bug.cgi?id=470503 appears to be fixed now)
 
(150 intermediate revisions by 17 users not shown)
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 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]].


== Session management ==
* Applications don't prompt to save unsaved work, causing data loss: https://bugs.kde.org/show_bug.cgi?id=461176
* 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.


== KWin/compositing/window management ==
== KWin/compositing/window management ==
* When the compositor crashes or restarts, non-Qt apps are killed — work is ongoing to fix this, see https://invent.kde.org/plasma/kwin/-/wikis/Restarting
* Worse performance on external monitor connected to NVIDIA GPU when default GPU is Intel: https://bugs.kde.org/show_bug.cgi?id=452219
* Not all Sticky Keys options work: https://bugs.kde.org/show_bug.cgi?id=444335
* 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
* Visual line glitches with certain fractional scale factors: https://bugs.kde.org/show_bug.cgi?id=465158
* "Spare Layouts" feature not implemented: https://bugs.kde.org/show_bug.cgi?id=455431
* Windows marked "keep on top" cover up panel widget pop-ups and clipboard history menu: https://bugs.kde.org/show_bug.cgi?id=466844
* Using key combination shortcuts to type phrases into windows is not yet implemented: https://bugs.kde.org/show_bug.cgi?id=478219
 
== 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)
 
== 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
* 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


== Plasma ==
== Upstream ==
* XEmbedSNIProxy window eats input in top-left pixel of the screen: https://bugs.kde.org/show_bug.cgi?id=433079
* Global Menu is broken for non-Qt apps: https://bugs.kde.org/show_bug.cgi?id=424485
* 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


== Upstream issues, or KDE issues blocked by required upstream changes ==
=== Waiting on new Wayland protocol ===
* No color management or support for changing Gamma: https://bugs.kde.org/show_bug.cgi?id=439135, https://bugs.kde.org/show_bug.cgi?id=439135, https://invent.kde.org/plasma/kwin/-/issues/11; requires https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14 and adoption in KWin
* 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.
* 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 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)
* QDockWidget does not visually move when moving and is not re-dockable when detached: https://bugreports.qt.io/browse/QTBUG-87332
* 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


== Specifically NVIDIA issues ==
=== Not yet started ===
* Sometimes Plasma fails to launch with Wayland and NVidia (kwin_scene_opengl: Creating the OpenGL rendering failed: "query surface failed"): https://bugs.kde.org/show_bug.cgi?id=440397
* 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.
* Plasma Panels sometime visually freeze: https://bugs.kde.org/show_bug.cgi?id=469016
* All screen content freezes when Night Color is activated: https://bugs.kde.org/show_bug.cgi?id=468895
* Also Night Color just doesn't work at all on Plasma Wayland with NVIDIA: https://bugs.kde.org/show_bug.cgi?id=450327
* Ghost trails/graphical glitches when waking from sleep: https://bugs.kde.org/show_bug.cgi?id=440397
* After waking NVIDIA-GPU-using system from sleep, sometimes text is partially or entirely missing from from QtQuick-based apps: https://bugs.kde.org/show_bug.cgi?id=451293


== Quality-of-life issues that aren't fully showstoppers ==
=== Work in progress ===
* Installed Chrome apps are grouped together with Chrome windows in Icon-Only Task Manager: https://bugs.kde.org/show_bug.cgi?id=358277
* 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
* Multiple Chrome windows on different virtual desktops causes heavy stuttering/freezing in Chrome. Does not occur if the multiple windows are on the same virtual desktop. Similar bug report filed for Ubuntu/Gnome/Wayland here: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1906792
* 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
* Windows that *are* session-restored 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
* Maximized XWayland apps leave pixel gaps when using a fractional scaling factor: https://bugs.kde.org/show_bug.cgi?id=459373
* Wrong app icon in Task Switcher for LibreOffice apps: https://bugreports.qt.io/browse/QTBUG-77182
* Some text copied from PDFs in Okular can't be pasted once Okular quits: https://bugs.kde.org/show_bug.cgi?id=468422


== Fixed already in Qt 6 but not backportable nor backported to Qt 5 ==
=== Fixed in an upcoming version ===
* plasmashell crashes when hovering or clicking items on the Panel due to "zwp_linux_buffer_params_v1.add" protocol error: https://bugs.kde.org/show_bug.cgi?id=447717; fixed in Qt 6.3
* 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
* Wrong positioning of context menu in multiple screens: https://bugs.kde.org/show_bug.cgi?id=436016 / https://bugreports.qt.io/browse/QTBUG-85297; fixed in Qt 6.4
* 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 - Implemented in Plasma 6.3.0 with KWin including support for the draft protocol. Apps can start implementing support too since the protocol is unlikely to change, and all that's left to get it completed is some XDG bureaucracy.
* When using a fractional scale factor, native Wayland apps are slightly blurry: https://bugs.kde.org/show_bug.cgi?id=446674; fixed in Qt 6.6
* 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 (Fixed in Qt 6.8.2)
* Changing scale causes Qt-based software to become blurry until restarted: https://bugreports.qt.io/browse/QTBUG-78327; fixed in Qt 6.6
* 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
* Apps using QDesktopServices::openUrl()/Qt.openUrlExternally don't raise existing windows in the activated app: https://codereview.qt-project.org/c/qt/qtwayland/+/321246 and https://codereview.qt-project.org/c/qt/qtbase/+/447556; fixed in Qt 6.5
* QMenus appear as standalone windows when opened using a stylus: https://bugreports.qt.io/browse/QTBUG-111130; fixed in Qt 6.6 - https://github.com/qt/qtwayland/commit/59fae923d72eaf640035237ae6ddb1ccfeba2210
* When the compositor crashes or restarts, Qt apps are killed - Fixed in Qt 6.5
* In multi-monitor setups with at least one scaled display, Context menus have items which are invisible until hovered: https://bugreports.qt.io/browse/QTBUG-93380 - Fixed in Qt 6.6

Latest revision as of 15:26, 18 December 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