STEPS TO REPRODUCE 1. Open System Settings 2. Change animation duration to anything other than its current value 3. Hit Meta+D OBSERVED RESULT The effect triggers with the old duration. EXPECTED RESULT The effect triggers with the new duration ADDITIONAL INFORMATION Restarting KWin or the computer makes it pick up the new duration.
animationDuration gets cached. This either needs re-evaluating on settings change or simply remove the caching.
I have found the root cause of the issue. In both EyeonScreenEffect and Windowaperture animation(belong to peek at Desktop animation) the config change signal is not connected to load config function of these animations at init. So if config change happens at runtime, it is not reflected because the signal is never captured to re-calculate the animation duration. Also found duplicate of this bug: 521002. I am submitting a Merge Request on KDE Invent to link against this ticket.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/9330
Created a merge request with fix: https://invent.kde.org/plasma/kwin/-/merge_requests/9330 Added single line for config change signal connection to load config in both windowaperture and eyeonscreen animation init function.
*** Bug 521002 has been marked as a duplicate of this bug. ***
Git commit e190e30deba32eb9cee547eb70dce1e96e93128c by Sudip Datta. Committed on 04/06/2026 at 11:10. Pushed by davidedmundson into branch 'master'. Add animation speed change signal in both peek at Desktop animation. In both animations configchanged signal was not tied to loadConfig. So at runtime animation speed change was not triggering config load. So they were running at old animation speed loaded at startup. Added both signal connection in init function M +1 -0 src/plugins/eyeonscreen/package/contents/code/main.js M +1 -0 src/plugins/windowaperture/package/contents/code/main.js https://invent.kde.org/plasma/kwin/-/commit/e190e30deba32eb9cee547eb70dce1e96e93128c