Overview
Better Blur DX replaces the default KWin blur effect and has some compatibility considerations with other effects. This page explains which effects conflict with Better Blur DX and how to resolve these issues.Incompatibility with Default KWin Blur
Since Better Blur DX effectively replaces the built-in KWin blur, you should never run both effects simultaneously. Using both effects at the same time will cause:- Double blurring: Some windows may be blurred twice, creating an overly blurred appearance that “looks off”
- Inconsistent behavior: Different windows may use different blur implementations, leading to visual inconsistencies
- Performance issues: Running two blur effects simultaneously doubles the GPU load unnecessarily
How to Properly Switch to Better Blur DX
- Open System Settings
- Navigate to Workspace → Desktop Effects
- Search for “blur” in the search box
- Disable the “Blur” effect (the default KWin blur)
- Enable the “Better Blur DX” effect
- Click Apply
Wobbly Windows Effect
The Problem
Better Blur DX blurs a rectangular region behind each window. When the Wobbly Windows effect is active, it deforms the window geometry, but the blur region remains rectangular. This creates two possible issues:- Blur bleeding: The rectangular blur region bleeds outside the deformed window shape, creating visible blur where it shouldn’t be
- Blur skipping: KWin may skip blur rendering entirely while the wobble animation is active, causing the blur to disappear during the animation
Visual Examples
Normal state (no wobble):Solutions
Option 1: Disable Wobbly Windows (Recommended) If you prefer consistent blur appearance, disable the Wobbly Windows effect:- Open System Settings → Workspace → Desktop Effects
- Find Wobbly Windows and disable it
- Click Apply
- Blur may temporarily disappear during window movements
- Visual artifacts around window edges are normal and expected
- This is a limitation of how the effects interact, not a bug
This is a fundamental limitation of how the two effects work. There are no plans to fix this issue, as it would require significant architectural changes to how blur regions are calculated.
Other Effect Conflicts
Better Blur DX should work correctly with most other KWin effects, including:- Desktop Cube: Works without issues
- Magic Lamp: Window animations work correctly with blur
- Fade: Fade effects work properly with blurred windows
- Scale: Overview and window scaling effects are compatible
- Glide: Window minimize/maximize animations work correctly
Testing New Effects
If you’re enabling a new effect and want to check compatibility with Better Blur DX:- Enable the new effect
- Test window operations that trigger the effect
- Watch for:
- Blur disappearing unexpectedly
- Visual artifacts or glitches
- Performance degradation
Third-Party Effects
If you’re using third-party KWin effects (effects not included with Plasma by default), be aware that:- These effects may not have been tested with Better Blur DX
- Effects that modify window shapes or rendering pipelines are most likely to cause issues
- Effects that only modify window behavior (not appearance) should work fine
- Disable the third-party effect temporarily to confirm it’s the cause
- Check if the third-party effect has any configuration options related to blur or window compositing
- Report the issue to both the Better Blur DX and third-party effect developers
Force Blur Feature
One of Better Blur DX’s key features is the ability to force blur on specific windows, even if they’re not transparent. This feature generally works well with other effects, but note:- Forced blur may interact unexpectedly with effects that modify window opacity
- If you’re seeing double blur on force-blurred windows, check that no other blur effects are enabled
- Window rules that modify opacity work correctly with force blur