Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
(Add https://bugs.kde.org/show_bug.cgi?id=454616 (Doesn't respect cursor theme at all))
Line 22: Line 22:


== System Settings ==
== System Settings ==
* Gamma KCM doesn't work/isn't visible
* Gamma KCM doesn't work/isn't visible: https://bugs.kde.org/show_bug.cgi?id=439135 & https://invent.kde.org/plasma/kwin/-/issues/11
* Graphic tablet KCM is very barebones compared to X11 version: https://bugs.kde.org/show_bug.cgi?id=433045
* Graphic tablet KCM is very barebones compared to X11 version: https://bugs.kde.org/show_bug.cgi?id=433045



Revision as of 09:46, 13 June 2022

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 Wayland goal.


Login/Session management

KWin/compositing/window management

  • When the compositor crashes or restarts, all apps are killed
  • Windows that were closed when maximized will open in the maximized position, but not the maximized state: https://bugs.kde.org/show_bug.cgi?id=437089
  • On Wayland, the compositor doesn't expose the minimized state. Some application and library code currently does things based on that state (usually to show their window again if needed, typically by calling QWidget::isMinimized()). Example: KNotifications' KStatusNotifierItem in KStatusNotifierItemPrivate::checkVisibility(...), invoked e.g. on clicking the item, uses the info to decide client-side whether to request showing the window again (or hide it)
  • In multi-monitor setups with at least one scaled display, Plasma context menus have items which are invisible until hovered: https://bugs.kde.org/show_bug.cgi?id=432264

Plasma

System Settings

Blocked on required upstream changes