Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
(Add https://bugs.kde.org/show_bug.cgi?id=447845 (XWayland-using Chromium web apps show the wrong icon))
No edit summary
Line 15: Line 15:
* Monitor connector names are different across X11 and Wayland, so logging into a Wayland session from X11 breaks multimonitor layout and Plasma configs: https://bugs.kde.org/show_bug.cgi?id=385135
* Monitor connector names are different across X11 and Wayland, so logging into a Wayland session from X11 breaks multimonitor layout and Plasma configs: https://bugs.kde.org/show_bug.cgi?id=385135
* 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
* XWayland-using Chromium web apps show the wrong icon: https://bugs.kde.org/show_bug.cgi?id=447845
* XWayland-using Chromium web apps show the wrong icon: https://bugs.kde.org/show_bug.cgi?id=447845


Line 32: Line 31:
* KDE app windows activated by Electron apps don't get brought forward due to lack of support for the Activation protocol in the toolkit: https://github.com/electron/electron/issues/30912
* KDE app windows activated by Electron apps don't get brought forward due to lack of support for the Activation protocol in the toolkit: https://github.com/electron/electron/issues/30912
* Picture-in-Picture windows from web browsers do not stay on top: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/44
* Picture-in-Picture windows from web browsers do not stay on top: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/44
* When a notification times out, it closes any context menus that are open and then blocks the next two right-clicks: https://codereview.qt-project.org/c/qt/qtwayland/+/347783
* When a notification times out, it closes any context menus that are open and then blocks the next two right-clicks: https://bugs.kde.org/show_bug.cgi?id=427542 / https://codereview.qt-project.org/c/qt/qtwayland/+/347783
* Installed Chrome apps do not show up as a unique app but instead assume the Chrome icon, in Icon-Only Task Manager: https://bugs.kde.org/show_bug.cgi?id=358277
* Installed Chrome apps do not show up as a unique app but instead assume the Chrome icon, in Icon-Only Task Manager: https://bugs.kde.org/show_bug.cgi?id=358277

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