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=477900 as a known upstream issue
Nicolas Fella (talk | contribs)
Move "Not all Sticky Keys options work" to non-Showstoppers. The basic functionality works, the rest needs input from affected people
Line 3: Line 3:
== True Showstoppers==
== 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:
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 ===
* Not all Sticky Keys options work: https://bugs.kde.org/show_bug.cgi?id=444335


== Non-showstoppers ==
== Non-showstoppers ==
Line 22: Line 19:
* Dialog Parent effect isn't working: https://bugs.kde.org/show_bug.cgi?id=460819
* Dialog Parent effect isn't working: https://bugs.kde.org/show_bug.cgi?id=460819
* Maximized XWayland windows have pixel gaps between screen edges when using a fractional scale factor: https://bugs.kde.org/show_bug.cgi?id=459373
* Maximized XWayland windows have pixel gaps between screen edges when using a fractional scale factor: https://bugs.kde.org/show_bug.cgi?id=459373
* Not all Sticky Keys options work: https://bugs.kde.org/show_bug.cgi?id=444335. Input on what is relevant/wanted there is welcome.


=== Plasma ===
=== Plasma ===

Revision as of 19:34, 17 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:

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

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