Comment 12 for bug 1917916

Config files have to be writable unless the file itself is correct. If file is not correct, timekpr will try to fix it and if file is not writable, problems arise :)
Obviously, any changes in administration application will require the file to be writable too.

If changes in config are done using GUI or CLI tools, you can deny writing to it right away, but if done manually in config file, I would suggest you wait one minute and only then deny writes to the file. This is due to 30 sec (default) reload interval if the file is modified externally.

To be precise, update solved only snap/flatpak process termination issue, there was nothing else ;)