Bug 431906 - changes in kwin kcm add unwanted AnimationDurationFactor to kwinrc, causing the global animation slider to not affect KWin animations
Summary: changes in kwin kcm add unwanted AnimationDurationFactor to kwinrc, causing t...
Status: RESOLVED DUPLICATE of bug 431259
Alias: None
Product: kwin
Classification: Plasma
Component: effects-various (show other bugs)
Version: 5.20.90
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
Depends on:
Reported: 2021-01-21 22:46 UTC by tempel.julian
Modified: 2022-06-16 10:14 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description tempel.julian 2021-01-21 22:46:31 UTC

When opened for the the first time, changing any setting on the kwin systemsettings kcm page seems to always add


to kwinrc when changing any setting. This e.g. causes the animation speed slider to stop working.

1. Check your kwinrc if there is the aforementioned entry and if it is, delete it and restart kwin.
2. Go to kwin kcm and change any setting.



is added to kwinrc.


This shouldn't happen to keep ability to change animation speed in systemsettings GUI.

Linux/KDE Plasma: Arch 5.10
KDE Plasma Version: 5.20.90 beta 1 Arch kde-unstable repo
Comment 1 Nate Graham 2021-01-22 15:04:22 UTC
Ooh that's bad. That's probably what's behind people having this in their kwinrc files and animations not going at the right speed. We've gotten a number of bug reports about this, so thanks for finding the root cause.

That said, which KCM makes this happen? There are multiple KWin-related KCMs. Can you narrow it down?
Comment 2 tempel.julian 2021-01-22 15:59:37 UTC
Ah yes: What I wanted to express was actually changing settings in systemsetting's kwin compositing kcm, e.g. changing latency policy.
I've also just tried with changes to virtual desktop config, which also trigger a compositing re-initialization, but they didn't add that faulty entry.
Comment 3 David Edmundson 2021-01-22 16:08:36 UTC
I've been wondering how this kept happening.

This makes sense.

kwincompositing contains the animation slider but hidden, so that we keep the option available for people who use kwin on $randomDesktop without having duplicates in kwin.

*IF* the value set in workspace settings is non default, we implicitly load that value when loading the settings

But if that differs from our local config we end up saving it there.
Comment 4 tempel.julian 2021-02-16 15:13:59 UTC
I can't reproduce anymore with 5.21 stable.
Comment 5 linuxatemyram 2022-01-21 17:53:18 UTC
*** Bug 448763 has been marked as a duplicate of this bug. ***
Comment 6 Vladimir Yerilov 2022-01-30 16:53:38 UTC
Whatever I do I can't reproduce it on 5.23.5, X session, systemd startup.
I had that "AnimationDurationFactor=0.5" initially, but it never appeared again after I removed it and started to change kwin settings.
Comment 7 Konstantin Kharlamov 2022-02-15 21:50:43 UTC
Given ~/.config/kwinrc file, neither can I reproduce it. I didn't have `AnimationDurationFactor` entry there and it doesn't appear when I change `systemsettings → Window Management → Window behavior → Window activation policy`.

Either it was fixed, or perhaps there was some specific setting, that upon change caused the offending line to be written in.

KDE Plasma version: 5.23.5
Comment 8 sn1128231220jd 2022-05-17 17:21:37 UTC
It seems like to reproduce this bug, the animation speed in the System Settings must first be set to a none-default value, after which changing anything in the Kwin kcm will cause the entry be added in kwinrc.
Comment 9 David Edmundson 2022-06-16 10:14:15 UTC

*** This bug has been marked as a duplicate of bug 431259 ***