Better Blur stopped working or being visible on Plasma 6.7.2.

[shahiljain]

Remcompiled using the aur as well but the option does not appear. Even after logouts.

[daveedmee]

You have to disable "hide incompatible effects" to see Better Blur DX.

[ParlDev]

Building it appears to error out

[daveedmee]

Wdym? I just built it and it works. What's the error you are getting?

[ParlDev]

Wdym? I just built it and it works. What's the error you are getting?

nvm I was being dumb and had the last version of Better Blur in my home directory

[Zedliminal]

I am having the same issue, I am able to have it show in settings by disabling the "exclude unsupported effects" option, but it is still not working.

[Reverrb]

Also experiencing this as of maybe 2-3 days ago. Just thought I'd chime in.

[shahiljain]

You have to disable "hide incompatible effects" to see Better Blur DX.

That does get the option to show up but I suppose it does not work with 6.7.2. yet

[Golotvinov]

You have to disable "hide incompatible effects" to see Better Blur DX.

That does get the option to show up but I suppose it does not work with 6.7.2. yet

Yes, the plugin appears, but the effect isn't applied. It doesn't work with Plasma 6.7.2

[bausensi]

it's broken again, is KDE making breaking changes to the blur yet again?

[Vertimyst]

Can confirm I'm also experiencing the same issue, Plasma 6.7.2 on CachyOS. I can build it and it does show up, but enabling it just leaves everything completely transparent, no blur effect is applied.

[DevKingofEarth]

Me too having the same problem. I use plasma 6.6.5 at nixos 26.05. I did try to logout and login. The issue persists.

[Infinality]

Yes, I have the same experience on Fedora. I'll wait for a fix before attempting to build packages for the repository.

[xarblu]

"It doesn't work" isn't really something I can work with. Does anyone have any more details ( logs, versions, etc.)?

[Golotvinov]

"It doesn't work" isn't really something I can work with. Does anyone have any more details ( logs, versions, etc.)?

Summary

kwin-effects-better-blur-dx (AUR, v2.5.1-1) stops working after a KWin point-release update (6.7.1 → 6.7.2), even with no change to the plugin package itself. Rebuilding the exact same package version against the newly-installed kwin headers, then restarting the KWin session, fixes it — pointing to a KWin effect-plugin ABI break between point releases rather than a bug in the effect's own logic.

Environment

• Distro: CachyOS Linux (Arch-based)
• Kernel: 7.1.2-3-cachyos
• Session: Wayland (KWin Wayland)
• kwin: 6.7.2-1.1
• plasma-workspace: 6.7.2-1.1
• kdecoration: 6.7.2-1.1
• qt6-base: 6.11.1-1.1
• kwin-effects-better-blur-dx: 2.5.1-1 (AUR)
• KWIN_EFFECT_API_VERSION on affected system (from /usr/include/kwin/effect/effect.h): MAJOR=0, MINOR=237

Timeline (from pacman.log)

• 2026-06-26: plasma-workspace/kwin upgraded 6.7.0 → 6.7.1
• 2026-06-28 21:07: kwin-effects-better-blur-dx 2.5.1-1 installed, built against kwin 6.7.1
• 2026-07-02 20:23: routine system update upgrades kwin 6.7.1 → 6.7.2 (plasma-workspace, kdecoration, etc. also bumped in lockstep)
• Immediately after this update, the blur effect stopped rendering. Effect-better-blur-dx remained enabled in kwinrc (better_blur_dxEnabled=true) throughout — this is not a config/settings issue.
• 2026-07-02 21:07: rebuilt the identical package version (yay -S kwin-effects-better-blur-dx --rebuild --noconfirm) against the now-installed kwin 6.7.2 headers → new .so produced and reinstalled
• After logging out and back in (full KWin restart), the effect works again

Observations

• No missing shared-library dependencies (ldd on better_blur_dx.so showed nothing unresolved).
• No explicit load-failure or error message for the plugin appeared und kwin/session startup — the effect just silently stopped applying. (Did not test with QT_LOGGING_RULES="kwin_*=true" for more verbose plugin-loading diagnostics — may be worth trying if you want a more precise failure log.)
• Only fix needed was a rebuild against current headers; no source cis is purely a binary/ABI compatibility issue, not a code regressionin the effect itself.
• Restarting KWin (kwin_wayland --replace or logout/login) is requuilt .so on disk isn't picked up by an already-running KWinprocess.

[xarblu]

Rebuilding the exact same package version against the newly-installed kwin headers, then restarting the KWin session, fixes it

That is always required on any KWin update anyways and not an issue with the effect itself.

I'm assuming others did rebuild and it's still not working? Any info from those?