Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
(Dump first note about challenge with client-side use of isMinimized)
(Move info added in prior change into the "KWin/compositing/window management" section)
Line 9: Line 9:
* When the compositor crashes or restarts, all apps are killed
* 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
* 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)


== Plasma ==
== Plasma ==
Line 24: Line 25:
* Apps gets stuck after dragging things out of them: https://bugs.kde.org/show_bug.cgi?id=446891
* Apps gets stuck after dragging things out of them: https://bugs.kde.org/show_bug.cgi?id=446891
* Can't abort drag-and-drop with the Esc key while dropped file is over Plasma panel or desktop: https://bugs.kde.org/show_bug.cgi?id=405267
* Can't abort drag-and-drop with the Esc key while dropped file is over Plasma panel or desktop: https://bugs.kde.org/show_bug.cgi?id=405267
== Client-side (un)minimize handling ==
* On Wayland, the compositor doesn't expose the minimized state
* Some application and library code currently does things based on that state though, 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)


== Qt/Wayland/other upstream ==
== Qt/Wayland/other upstream ==

Revision as of 14:46, 24 December 2021

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)

Plasma

System Settings

Drag and Drop issues

Qt/Wayland/other upstream