https://bugs.kde.org/show_bug.cgi?id=481113
--- Comment #58 from David Edmundson <k...@davidedmundson.co.uk> --- Doing it on shutdown *as well* is fine, it not syncing when a change happens isn't design, it's a bug in the code somewhere. Identified. On config change, the signal propagates up to CoronaPrivate::syncConfig but no-one is ever calling Applet::save(). We're writing the config to disk, but without syncing between the KConfigLoader and the KConfig. Adding saveLayout(q->config()); to CoronaPrivate::syncConfig before the config()->sync() seems to resolve it. but it's definitely not a right fix as saveConfig is also emitting propagateConfigChanged, which is semantically what triggers a sync to disk. I don't understand what this current code is trying to do, will need to do some archeology first. -- You are receiving this mail because: You are watching all bug changes.
