Bug 480611

Summary: Screen dims when adding filter layers, preventing user from accurately previewing effect
Product: [Applications] krita Reporter: Nathan Upchurch <nathan>
Component: Filter LayersAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: cromachina, griffinvalley
Priority: NOR    
Version First Reported In: 5.2.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Nathan Upchurch 2024-01-31 17:30:59 UTC 
STEPS TO REPRODUCE
1. Open an image in Krita
2. Using the layers panel, add a new filter layer
3. Observe the screen dimming as dialog opens

OBSERVED RESULT
Screen dimming prevents user from accurately previewing the effect of the filter when adjusting settings

EXPECTED RESULT
Screen does not dim, so that user can accurately preview the effect of the filter

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.114.0
Qt Version: 5.15.12
Kernel Version: 6.7.1-arch1-1 (64-bit)
Graphics Platform: X11
Comment 1 wolthera 2024-01-31 17:31:59 UTC 
Hi,

Krita doesn't control this, rather, it is an option in your window compositor when using modal windows. You will have to configure it there.
Comment 2 Nathan Upchurch 2024-01-31 17:41:10 UTC 
(In reply to wolthera from comment #1)
> Krita doesn't control this, rather, it is an option in your window
> compositor when using modal windows. You will have to configure it there.

I see; thanks for the information. I found the setting in Desktop Effects > Focus > Dialog Parent. It doesn't appear that there's any way to keep this behavior for all windows except Krita, barring disabling compositing via 'Configure Special Application Settings' in the window decoration context menu.
Comment 3 dra.w.p.il.e+bugskde 2025-10-23 23:54:41 UTC 
*** Bug 510986 has been marked as a duplicate of this bug. ***
Comment 4 dra.w.p.il.e+bugskde 2025-10-24 01:36:25 UTC 
*** Bug 510986 has been marked as a duplicate of this bug. ***