Jump to content

Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
Meven (talk | contribs)
Eiglow (talk | contribs)
Added https://bugs.kde.org/show_bug.cgi?id=449163 because I've encountered it repeatedly on multiple systems now
Line 19: Line 19:
* When using scaling, scale is reset and re-applied on login, causing various issues: https://bugs.kde.org/show_bug.cgi?id=449212
* When using scaling, scale is reset and re-applied on login, causing various issues: https://bugs.kde.org/show_bug.cgi?id=449212
* Some apps don't appear in Task Manager: https://bugs.kde.org/show_bug.cgi?id=444325
* Some apps don't appear in Task Manager: https://bugs.kde.org/show_bug.cgi?id=444325
* Panel becomes unresponsive after an indefinite amount of time: https://bugs.kde.org/show_bug.cgi?id=449163


== System Settings ==
== System Settings ==

Revision as of 11:57, 6 February 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)

Plasma

System Settings

Drag and Drop issues

Qt/Wayland/app-specific/other upstream or downstream issue