Created attachment 155998 [details] Showcase of the bug - notice how the newly launched instance is not affected by it SUMMARY After a while, the blur effect stops rendering properly and starts glitching out (switching between opaque and blurred). This effect is isolated to a particular application (window?) and disappears once the application is restarted, or a new instance launched. The glitch also affects context (right-click) menus, which can either become entirely opaque, or glitch out when hovering over different elements. So far, I've encountered this glitch with: dolphin, keepassxc, plasmashell (context menus e.g. when right-clicking desktop would turn opaque, and be blurred again upon restarting plasmashell). Though I assume anything that can be blurred can be affected by this. The X11 session is not affected by this as far as I can tell. STEPS TO REPRODUCE Currently unclear what exactly provokes the glitch. It may be related to the amount of time the application has been open, or it may be caused by the display turning off and on again. OBSERVED RESULT Blur effect glitches (see video attachment) EXPECTED RESULT Blur effect does not glitch SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo (available in About System) KDE Plasma Version: 5.27 beta KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Mesa: 23.0.0_rc4 Kernel: 6.1.9 GPU: AMD ATI Radeon RX 7900 XTX ADDITIONAL INFORMATION -
Further testing indicates this is probably related to the display turning on / off. As the glitch happened again (with dolphin), I manually turned the display off and then on again, after which Dolphin's window was out of bounds (outside the screen). I managed to get it back to the screen by right clicking in the task manager and selecting More Actions -> Move. Once it returned, the blur was being rendered normally again. Not sure if the window going out of bounds and the blur glitch are at all related, but it was the only window to go out of bounds and it just so happened to also be the only one affected by the blur glitch at the time. Will update with more info as I uncover it.
*** This bug has been marked as a duplicate of bug 455526 ***