Plasma/Wayland Known Significant Issues: Difference between revisions

Revision as of 14:48, 9 November 2019

This page tracks the Wayland showstoppers through out the stack

General 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).

No Drag and Drop between Wayland native and Xwayland clients

~~From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.~~

Fixed in Plasma 5.16

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.

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.

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: To EGL Stream or Not and Plasma/Wayland and NVIDIA – 2017 edition

Partly fixed initial support was added in Plasma 5.16

No Clipboard Manager protocol

No clipboard history (e.g. Klipper and clipboard plasmoid) and no clipboard sync with KDE Connect.

In progress: https://phabricator.kde.org/T4449

Input

No (wacom) Tablet support

KWin lacks integration the tablet support from libinput. Also KWayland lacks wrapping the API for it.

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 xkbcommon-issue40 --> Explain how this issue is related?

Plasma

Native Wayland windows are not restored

Session restoring does not include Wayland native windows. Our sessions management recover engine is based on the 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 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.

Logout

~~There's a crash I know (but fixing properly breaks X). Might be more stuff with SDDM, needs investigation~~

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

No animated cursors

~~See QTBUG-48181~~

Fixed in Qt 5.14

Key repeat not working

~~See QTBUG-55615~~

Fixed in Qt 5.13

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

~~see QTBUG-63748~~

Fixed in Qt 5.12

@@ Line 36: / Line 36: @@
 == Plasma ==
-=== <s>Virtual Desktops</s> ===
-<s>We don't have an API yet for virtual desktops, so pager is not working</s>
-'''Fixed''' in Plasma 5.15
 === 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.