https://bugs.kde.org/show_bug.cgi?id=422625
--- Comment #6 from Ilya Bizyaev ---
I suspect there's some KWin bug still involved here since the issue occurs when
the effect shouldn't even be triggered and persists for the whole session
afterward. But I don't know enough of what KWin scripting API
https://bugs.kde.org/show_bug.cgi?id=422625
Nate Graham changed:
What|Removed |Added
Resolution|--- |DOWNSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=422625
--- Comment #4 from Ilya Bizyaev ---
> Do you see some other unusual things, e.g. high CPU usage, etc?
No, as I mentioned, all observable resources are fine...
But I managed to find the reason: the issue was somehow caused by a popular
KWin script call
https://bugs.kde.org/show_bug.cgi?id=422625
--- Comment #3 from Vlad Zahorodnii ---
> affect the mouse cursor, but it always affects window contents.
Urgh, it could be that I broke it :/
Do you see some other unusual things, e.g. high CPU usage, etc?
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=422625
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Priority|NOR
https://bugs.kde.org/show_bug.cgi?id=422625
--- Comment #2 from Ilya Bizyaev ---
The key seems to be in the maximize animation itself, when kwin animates the
future region for the app. Just reproduced with Telegram as well.
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=422625
--- Comment #1 from Ilya Bizyaev ---
Replacing KWin seems to also help now; didn't help earlier, maybe is somehow
related to x11 downgrade.
Anyway, I have found one way to consistently reproduce this on my machine:
restore and then maximize Firefox wit
