Kontact loses settings like activated / checked calendar or address book resources as well as layout changes like shifted panes when KDE shuts down. I have Kontact permanently running and do not close it prior shutting down so it gets automatically restored on restart. However, these mentioned settings only get properly persisted when I manually close Kontact. Reproducible: Always Steps to Reproduce: 1. Change any layout property of any of the plugins or activate / deactivate a calendar or addressbook 2. Shutdown PC / KDE 3. Restart Actual Results: The applied changes are lost. Expected Results: Kontact should persist these changes right away so a forceful shutdown does not discard them. Maybe KDE should also just wait for applications to stop properly instead of just killing them.
This bug is especially a nuisance since one of my most important calendars is hosted online on an ownCloud server. The calendar gets randomly deactivated from time to time (checkmark is automatically removed from the checkbox and I really have not the slightest clue why). When I happen to notice that problem it does not suffice to just check that box again. I need to check it, close Kontact start it again and hope for the best. But unfortunately another unrelated bug makes calendar notifications in Kontact also pretty much useless. Your computer needs to be switched on at the point in time the appointment notification kicks in. It does not notify you about alarms that started slightly in the past. Kontact used to work years ago. I could rely on not missing a single calendar event notification. Also simple stuff like email recipient auto-completion used to work. Kontact felt solid, reliable and well-made. Since the migration to Akonadi that changed dramatically.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.