Created attachment 153974 [details] Window content blur demonstration. SUMMARY *** As mentioned in the title, window contents become blurry when restoring a maximized window by dragging the title bar. The amount of blur seems to vary each time I try this but it happens basically every time I do it. This happens only with compositing enabled. To me it seems like window coordinates are not rounded to full pixels and due to this subpixel shift to the window coordinates it appears blurry. E.g. when I screenshot only the blurred window with spectacle, it appears sharp, but when I screenshot the whole desktop the blur is visible. *** STEPS TO REPRODUCE See the attached video for a demonstration which also includes the steps to reproduce. Please watch it at native 1920x1080 resolution without scaling to better see the difference in sharpness. OBSERVED RESULT Window contents appear blurry. EXPECTED RESULT Window contents appear sharp with no additional blur added by the compositor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux / 5.26.3 (available in About System) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7+kde+r175-1
I just checked and this also happens with the wayland session.
In search of a workaround for this I found out that the bug only happens with the following setting: window behaviour --> movement --> screen edge snap zone := None (This is roughly translated from german where it's called "Fensterverwaltung --> Fensterverhalten --> Verschiebung --> Bildschirmrand-Einrastzone".) When setting this to 1px or using the default value of 10px, the blurriness can be avoided.
Possibly related to Bug 461283, maybe?
Confirmed for me. It also happens in firefox (or all gtk apps?) that uses CSD when you unmaximize them. Worst part is that firefox stays blurry until maximized again or compositor not disabled ofc.
We made some changes in Plasma 5.27 that should help with this case. Please reopen if an issue persists in the new release with a new screenshot.
*** Bug 465382 has been marked as a duplicate of this bug. ***