Jump to content

Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
Ngraham (talk | contribs)
No edit summary
Ngraham (talk | contribs)
Add https://bugs.kde.org/show_bug.cgi?id=447845 (XWayland-using Chromium web apps show the wrong icon)
Line 16: Line 16:
* XEmbedSNIProxy window eats input in top-left pixel of the screen: https://bugs.kde.org/show_bug.cgi?id=433079
* XEmbedSNIProxy window eats input in top-left pixel of the screen: https://bugs.kde.org/show_bug.cgi?id=433079
* Context menus and tooltips disappear when any notifications on screen disappear: https://bugs.kde.org/show_bug.cgi?id=427542
* Context menus and tooltips disappear when any notifications on screen disappear: https://bugs.kde.org/show_bug.cgi?id=427542
* XWayland-using Chromium web apps show the wrong icon: https://bugs.kde.org/show_bug.cgi?id=447845


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

Revision as of 19:04, 13 January 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