Bug 454453 - Window decoration Blur effect does not work with new setBlurRegion() API on 5.24.90, but always worked on 5.24.80 git master
Summary: Window decoration Blur effect does not work with new setBlurRegion() API on 5...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: effects-various (show other bugs)
Version: 5.24.90
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2022-05-26 21:22 UTC by Paul McAuley
Modified: 2022-05-31 22:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul McAuley 2022-05-26 21:22:48 UTC
I have implemented the new setBlurRegion() API for my C++ window decoration (https://github.com/paulmcauley/classik). This (mostly https://bugs.kde.org/show_bug.cgi?id=453229) works fine on the git master (and has for a month or so now), with a blur effect that matches the window shape. 

However, when I enable transparency and blur in my window decoration (this simply calls setBlurRegion() with the window shape) on the 5.24.90 beta I do not get any blur at all, just transparency. 

I have removed the "blur":true line from my .json file (as done by Michail Vourlakos for Aurorae) . Readding "blur": true to the .json enables blur again on 5.24.90, but with the kornerbug that the new setBlurRegion API was designed to fix (https://bugs.kde.org/show_bug.cgi?id=395725).


Operating System: openSUSE Leap 15.3
KDE Plasma Version: 5.24.90
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.3.18-150300.59.68-preempt (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630
Manufacturer: Dell Inc.
Product Name: XPS 15 9560
Comment 1 Paul McAuley 2022-05-31 22:44:24 UTC
I have noticed with the latest kwin update on 5.24.90 from OpenSUSE that this has been fixed.

Closing