Jump to content

Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
Apol (talk | contribs)
Apol (talk | contribs)
No edit summary
Line 7: Line 7:
* Cursor lags under high CPU load: https://bugs.kde.org/show_bug.cgi?id=421131
* Cursor lags under high CPU load: https://bugs.kde.org/show_bug.cgi?id=421131
* "Pin/keep open" functionality for Plasma applets does not work: https://bugs.kde.org/show_bug.cgi?id=400317
* "Pin/keep open" functionality for Plasma applets does not work: https://bugs.kde.org/show_bug.cgi?id=400317
== Remote control support incomplete ==
* 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).


== Input ==
== Input ==

Revision as of 15:51, 24 January 2021

This page tracks the Wayland showstoppers throughout the stack.

KWin/compositing/window management

Input

  • 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.
  • No XModmap; we lack a functionality like XModmap to remap keys.
  • Can't type accented characters in native Wayland Qt apps: https://bugs.kde.org/show_bug.cgi?id=411729

Plasma

  • 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 activities.
  • Session sometimes crashes when changing Global Themes: https://bugs.kde.org/show_bug.cgi?id=422424

Drag and Drop issues