Created attachment 144947 [details]
Demonstation of this zooming bug
Blurry background is broken with Zoom KWin effect.
STEPS TO REPRODUCE
1. Open any applet from system tray (Show hidden icons works too)
2. Zoom in (Meta++), assuming the default "Zoom" variant — not a Magnifier, nor a Looking Glass.
3. Move cursor around
Background is misrendered: sometimes as mis-positioned blur (as if it follows the direction opposite to the cursor's movements), in other cases it may not even be blurred at all.
Should not glitch like that.
Operating System: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.15.11-arch2-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 970M/PCIe/SSE2
Git commit 544760469dd4fd7550fc7121250e694a485d453f by Vlad Zahorodnii.
Committed on 24/05/2022 at 13:11.
Pushed by vladz into branch 'Plasma/5.25'.
effects/zoom: Render scene in an offscreen texture
This fixes integration of the zoom effect with the blur effect and qtquick
effects such as overview or window view.
The main con of the proposed solution is that offscreen rendering can be
a bit overkill. But on the other hand, it's the most robust way to
ensure that fullscreen effects integrate correctly with the zoom effect.
For example, without it, the quick scene effect would need to figure out
what screen views to paint for the given screen. There are also more
finicky cases, e.g. the screen transform effect.
Related: bug 447002, bug 453467
Tested-by: Merge Service <https://invent.kde.org/plasma/kwin/-/merge_requests/2451>
(cherry picked from commit 221f114d8045f22eca722a4ce385367f4c3f03fc)
M +100 -24 src/effects/zoom/zoom.cpp
M +13 -0 src/effects/zoom/zoom.h
OMG, this is so cool! Can't wait to get home and test it out. Thanks!
Is this also resolving this bug I reported in 2010 for KDE 4.5 ?
That would be awesome!
> Is this also resolving this bug I reported in 2010 for KDE 4.5 ?
Looks like it. Although to be honest, I never experienced such a hard glitch as left-lover image trail on the first screenshot. Mind if we mark it as #resolved #fixed or #duplicate regardless?
*** Bug 241557 has been marked as a duplicate of this bug. ***