SUMMARY KOrganizer regularly forget what calendar was enabled and all calendars remain unchecked. STEPS TO REPRODUCE Hard to reproduce, but I suspect this happens when KOrganizer crashes for whatever reason. That is what happened just now: some calendars were enable, removed an event. While Kontact was in the background, it crashed. After restarting no calendars were enabled. This bug is not recent, it is around for a very long time. OBSERVED RESULT All calendars are unchecked. EXPECTED RESULT It should keep the state the user selected. SOFTWARE/OS VERSIONS KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 akonadiserver 6.0.0
https://bugs.kde.org/show_bug.cgi?id=456717 looks related
A possibly relevant merge request was started @ https://invent.kde.org/pim/korganizer/-/merge_requests/120
Git commit f1cd0d65af952d8a00efc7dc0d90e9ef1dba471c by Carl Schwan, on behalf of Daniel Vrátil. Committed on 27/03/2024 at 08:45. Pushed by carlschwan into branch 'release/24.02'. Save calendar selection on change instead of on exit Ensures that the calendar selection is preserved even when KOrganizer crashes or user kills it. FIXED-IN: 24.02.2 M +4 -0 src/actionmanager.cpp https://invent.kde.org/pim/korganizer/-/commit/f1cd0d65af952d8a00efc7dc0d90e9ef1dba471c
I don't have enough info to reopen, but I add a not, that this happened again: - added some google calendar items - hibernated the machine - next day switched to To-Do list -> crash - restarted Kontact, switched to todo list -> crash - restarted Kontact, didn't crash this time, but the calendars I enabled were again disabled
I fixed that last week: https://invent.kde.org/pim/akonadi-calendar/-/merge_requests/89
For some reason, Carl's fix only went to the 24.02 branch, not to master. But if I may say so, I prefer my fix. It reacts only on actual user interaction, while connecting to selectionChanged() worries me that it'll save partial state while loading the selection (by reacting at every step).