Jump to content

Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
← Older edit
Ngraham (talk | contribs)
KDEDevelopers, Administrators, trusted
1,822 edits
MartinR (talk | contribs)
KDEDevelopers, trusted
280 edits
m →Accessibility: Add link to merge request for moving pointer with numpad keys
 
(618 intermediate revisions by 42 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]].
=== NVIDIA ===
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]


=== NVIDIA + XWayland ===
XWayland also uses the DRM/GBM mechanism. Due to that XWayland is not supporting OpenGL on NVIDIA even if KWin would support NVIDIA's eglstream. This would result in a terrible experience for all gamers.


=== QT_QPA_PLATFORM ===
== KWin/compositing/window management ==
QT_QPA_PLATFORM is set to wayland breaking any application which has Qt included (e.g. appimages, proprietary software) and doesn't have wayland QPA.
* 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


=== No remote support ===
We don't have an API yet for remote support. Even if we had things like TeamViewer would not work any more.


== Input ==
== Accessibility ==
=== No (wacom) Tablet support ===
* 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]
KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.
* 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 configurable gestures ===
== Graphics Tablet Support ==
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.
* 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
* 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


=== No XModmap ===
We lack a functionality like XModmap to remap keys.


== Plasma ==
== Upstream ==
=== Virtual Desktops ===
We don't have an API yet for virtual desktops, so pager is not working


=== No window thumbnails ===
=== Waiting on new Wayland protocol ===
We don't have an API yet for window thumbnails.
* 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)
* 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


=== No window move on empty area in breeze ===
=== GTK ===
Broke with switch to XdgShellV6. Needs new API added to Qt (native interface), KWayland and Breeze.
* 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.
* 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


=== Logout ===
=== NVIDIA ===
[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
* Worse performance on external monitor connected to NVIDIA GPU when default GPU is Intel: https://bugs.kde.org/show_bug.cgi?id=452219
 
=== 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 ==
=== No animated cursors ===
See [https://bugreports.qt.io/browse/QTBUG-48181 QTBUG-48181]
 
=== wl_proxy_create_wrapper  ===
http://bugs.kde.org/381630 (Fixed in Qt 5.9.5)
 
=== Key repeat not working ===
See [https://bugreports.qt.io/browse/QTBUG-55615 QTBUG-55615]
 
=== Compose key not working ===
Will be fixed in Qt 5.11, [https://wiki.qt.io/Qt_5.11_Release expected May 2018]. See [https://bugreports.qt.io/browse/QTBUG-54792 QTBUG-54792]


=== No tablet support ===
QtWayland does not yet support the tablet API. So even if KWin had support Qt would not be able to use it.


=== Fullscreen does not work ===
== Fixed in an upcoming version ==
see [https://bugreports.qt.io/browse/QTBUG-63748 QTBUG-63748]
* 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

Latest revision as of 11:46, 12 February 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.


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

GTK

NVIDIA


Fixed in an upcoming version

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