Plasma/Wayland Known Significant Issues: Difference between revisions
Remove Xwl paragraph - might be possible now |
|||
| Line 4: | Line 4: | ||
=== NVIDIA === | === 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] | 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] | ||
=== QT_QPA_PLATFORM === | === QT_QPA_PLATFORM === | ||
Revision as of 10:13, 13 June 2018
This page tracks the Wayland showstoppers through out the stack
General 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: To EGL Stream or Not and Plasma/Wayland and NVIDIA – 2017 edition
QT_QPA_PLATFORM
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.
Fixed by not setting the variable in system, but let every app decide on itself. With 5.11 setting this variable is not needed at all anymore, because it autodetects the windowing system.
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.
No vertical / horizontal maximize of Wayland native clients
KWin uses NetWM modes internally to do this. Works with Xwayland clients.
Drag and Drop between Wayland native and Xwayland apps not working
From Wayland to Xwayland ignores. From Xwayland to Wayland falls through.
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
Virtual Desktops
We don't have an API yet for virtual desktops, so pager is not working
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
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
wl_proxy_create_wrapper
Fixed in Qt 5.9.5
Key repeat not working
See QTBUG-55615
Compose key not working
Will be fixed in Qt 5.11, expected May 2018. See QTBUG-54792
Fixed in Qt 5.11
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