https://bugs.kde.org/show_bug.cgi?id=522547
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Latest Commit| |https://invent.kde.org/fram | |eworks/kwindowsystem/-/comm | |it/7de6ab4cecbc00896ecf98da | |666132e011573025 Resolution|--- |FIXED --- Comment #17 from [email protected] --- Git commit 7de6ab4cecbc00896ecf98da666132e011573025 by Anton Karasev. Committed on 08/10/2026 at 13:28. Pushed by zamundaaa into branch 'master'. platforms/wayland: Don't create a background effect to remove the blur enableBlurBehind(window, false) destroys the background effect of the window and stops watching the window, then installBlur() created a new ext_background_effect_surface_v1 for it only to set a null blur region. When the surface of the window was destroyed, for example when a popup is closed with QWindow::close(), nothing reset that object, so the next enableBlurBehind(window, true) set a blur region on an inert object and the compositor disconnected the client with "tried to set blur region on destroyed surface". Destroying the object already removes the blur, so don't create a new one. This also removes the blur when the compositor withdraws the blur capability, which used to leave the old region in place. M +4 -0 src/platforms/wayland/windoweffects.cpp https://invent.kde.org/frameworks/kwindowsystem/-/commit/7de6ab4cecbc00896ecf98da666132e011573025 -- You are receiving this mail because: You are watching all bug changes.
