Plasma/Wayland Known Significant Issues: Difference between revisions

From KDE Community Wiki
(https://bugs.kde.org/show_bug.cgi?id=402903#c7)
Line 4: Line 4:
* When the compositor crashes, all apps crash too: https://bugreports.qt.io/browse/QTBUG-85631
* When the compositor crashes, all apps crash too: https://bugreports.qt.io/browse/QTBUG-85631
* No Wayland protocol for cross-app window activation/focus, so windows don't get brought forward when activated by another app: https://bugs.kde.org/show_bug.cgi?id=424795 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/50
* No Wayland protocol for cross-app window activation/focus, so windows don't get brought forward when activated by another app: https://bugs.kde.org/show_bug.cgi?id=424795 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/50
* No Wayland protocol for app launch feedback, so there is no feedback on the cursor or Task Manager when an app is launched: https://bugs.kde.org/show_bug.cgi?id=402903
* No Wayland protocol for app launch feedback, so there is no feedback on the cursor or Task Manager when an app is launched: https://bugs.kde.org/show_bug.cgi?id=402903 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/50
* "Pin/keep open" functionality for Plasma applets does not work: https://bugs.kde.org/show_bug.cgi?id=400317
* "Pin/keep open" functionality for Plasma applets does not work: https://bugs.kde.org/show_bug.cgi?id=400317
* Very blurry fractional scaling for native Wayland windows due to using a downsampled 2x or 3x pixmap: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/34
* Very blurry fractional scaling for native Wayland windows due to using a downsampled 2x or 3x pixmap: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/34

Revision as of 13:23, 18 March 2021

This page tracks the Wayland showstoppers throughout the stack.

KWin/compositing/window management

Input

Plasma

Drag and Drop issues