Jump to content

Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
Ngraham (talk | contribs)
Mention https://bugs.kde.org/show_bug.cgi?id=451158 as an upstream issue in GTK and Electron
Ngraham (talk | contribs)
No edit summary
Line 45: Line 45:
* When using a Chromium-based browser in native Wayland mode, dragging an image to the desktop creates a sticky note out of it: https://bugs.kde.org/show_bug.cgi?id=449645
* When using a Chromium-based browser in native Wayland mode, dragging an image to the desktop creates a sticky note out of it: https://bugs.kde.org/show_bug.cgi?id=449645
* When dragging images from Firefox to the desktop, have to hold the drag 1 or more seconds over the desktop before releasing or else the desktop drop menu does not appear: https://bugs.kde.org/show_bug.cgi?id=448867
* When dragging images from Firefox to the desktop, have to hold the drag 1 or more seconds over the desktop before releasing or else the desktop drop menu does not appear: https://bugs.kde.org/show_bug.cgi?id=448867
* With screen scaling, cursor size is incorrect when hovering over native Wayland apps written with the GTK and Electron toolkits due to their lack of support for the cursor-shape-v1 protocol: https://bugs.kde.org/show_bug.cgi?id=451158
* With screen scaling, cursor size is incorrect when hovering over native Wayland apps written with the GTK and Electron toolkits due to their lack of support for the cursor-shape-v1 protocol: https://bugs.kde.org/show_bug.cgi?id=451158. See also https://bugs.kde.org/show_bug.cgi?id=459161 for general cursor size issues.


== Fixed upstream in Qt 6 ==
== Fixed upstream in Qt 6 ==

Revision as of 16:42, 11 December 2023

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.

True Showstoppers

These are the issues that must be fixed before we can recommend Wayland by default. The current plan is to flip the switch before the Alpha release, but then revert that change if we don't have all of these issues fixed before the first beta:

KWin/compositing/window management

Non-showstoppers

This is effectively an "Errata/Known issues" list: quality-of-life annoyances, problems with workarounds, etc. Don't expect all or even any of these to be fixed before we go wayland-by-default.

Session management

KWin/compositing/window management

Plasma

NVIDIA

Upstream, not fixed yet

Fixed upstream in Qt 6

These are fixed in Qt 6 but neither backportable nor backported to Qt 5.