https://bugs.kde.org/show_bug.cgi?id=450672
Fushan Wen <qydwhotm...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Latest Commit| |https://invent.kde.org/plas
| |ma/plasma-workspace/commit/
| |4cd6ec7446b65213448530a64d5
| |84b54268a5ef4
Resolution|--- |FIXED
--- Comment #11 from Fushan Wen <qydwhotm...@gmail.com> ---
Git commit 4cd6ec7446b65213448530a64d584b54268a5ef4 by Fushan Wen, on behalf of
Vlad Zahorodnii.
Committed on 23/02/2022 at 09:24.
Pushed by fusionfuture into branch 'master'.
Make DesktopView set black clear color only on Wayland
745e2c08289b35ccd007cf436f653a6e92b45ef9 made DesktopView set clear
color to "black" so the compositor could avoid overdraw and thus
optimizing rendering. In the perfect world, such a change would create
no regressions, but for some reason, it made panels lose alpha channel
on X11.
That makes absolutely no any sense. DesktopView and PanelView are two
totally different code paths. So changes in DesktopView should not
affect the PanelView. This looks like a QtXCB bug.
Ideally, we should add workarounds only after finding what creates a
problem, but this one is particularly hard because many people who have
tried to reproduce that issue weren't successful. Somebody who can
reproduce the issue would have to be able to build Qt from source code
and add qDebug()s. These requirements are too steep, thus adding a
platform check seems like the best option at the moment.
M +6 -1 shell/desktopview.cpp
https://invent.kde.org/plasma/plasma-workspace/commit/4cd6ec7446b65213448530a64d584b54268a5ef4
--
You are receiving this mail because:
You are watching all bug changes.
