Occasionally I'm using the calendar event reminders as a TODO list ("remind me later"). As soon as the last such reminder has been delayed again, the korgac window closes and there doesn't seem to be a way to bring it back. Left-clicking on it brings up the task list in Kontact (which is not related at all to the calendar in my case) and the RMB context menu also doesn't seem to contain a function to show the reminders.
Beside this temporary inaccessibility, there seems to be a permanent one: If there are past reminders which have been delayed, the respective reminders are not shown again after a system reboot. This makes it hard to track back manually in the calendar which TODOs were still open. To give an example, there's an entry in korgacrc:
Which resolves to the following entry in std.ics:
SUMMARY: Integration ownCloud
This event has definitely not shown up in my reminders list for many weeks. And I didn't perform the ownCloud integration job due to the missing reminder :)
The system runs KDE 4.7 but with KDEPIM being at 4.4.11 (Debian packaging default).
Git commit d1d99767eed455ee6f152ca9b7461f7a9a9acaa0 by Frank Roscher.
Committed on 05/12/2012 at 20:18.
Pushed by froscher into branch 'master'.
Fix saving and loading of suspended reminders in KOrganizer
We need to wait for all collections to be available when restoring
reminders at startup, or they won't get loaded properly. Additionally,
we must delete reminders one by one as they are dismissed instead of
just cleaning out the config file after each startup.
Related: bug 280321, bug 146336, bug 180413
M +2 -3 korganizer/korgac/alarmdialog.cpp
M +50 -29 korganizer/korgac/koalarmclient.cpp
M +2 -0 korganizer/korgac/koalarmclient.h
Frank, can we resolve this as fixed?
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 korgac (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.