Jump to content

Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
Ngraham (talk | contribs)
No edit summary
Ngraham (talk | contribs)
No edit summary
Line 29: Line 29:
* 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


== Qt/Wayland/app-specific/other upstream or downstream issue ==
== Blocked on required upstream changes ==
* When using any scale factor above 100%, XWayland apps are blurry from being upscaled from the 100% version: https://bugs.kde.org/show_bug.cgi?id=446674; requires https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/733
* When using any scale factor above 100%, XWayland apps are blurry from being upscaled from the 100% version: https://bugs.kde.org/show_bug.cgi?id=446674; requires https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/733
* When using a fractional scale factor, native Wayland apps are slightly blurry: https://bugs.kde.org/show_bug.cgi?id=446674; requires  https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/34
* When using a fractional scale factor, native Wayland apps are slightly blurry: https://bugs.kde.org/show_bug.cgi?id=446674; requires  https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/34
* No color management: https://bugs.kde.org/show_bug.cgi?id=439135 / https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14
* No color management: https://bugs.kde.org/show_bug.cgi?id=439135; requires https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14
* KDE app windows don't get brought forward when activated by another KDE app: https://codereview.qt-project.org/c/qt/qtwayland/+/321246 (in review: ; support will come sometime for Qt 6)
* KDE app windows don't get brought forward when activated by another KDE app: requires Qt6; support was added in https://codereview.qt-project.org/c/qt/qtwayland/+/321246
* 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://bugs.kde.org/show_bug.cgi?id=427542 / 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; requires 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
* Wrong positioning of context menu in multiple screens https://bugreports.qt.io/browse/QTBUG-85297 (<s>https://bugs.kde.org/show_bug.cgi?id=436016</s>)
* Wrong positioning of context menu in multiple screens: https://bugs.kde.org/show_bug.cgi?id=436016; requires https://bugreports.qt.io/browse/QTBUG-85297

Revision as of 21:23, 11 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

Blocked on required upstream changes