REPRODUCIBILITY (% or how often): 100%
BUILD ID = OS VERSION (Settings > About product): 4.2.0.21
HARDWARE (XA2, X10, X10 II, …): XA2 Plus dual sim
UI LANGUAGE: French
REGRESSION: (compared to previous public release: Yes, No, ?): Yes (from 3.x)
DESCRIPTION:
Calendar reminders are triggered for deleted calendar accounts
PRECONDITIONS:
STEPS TO REPRODUCE:
Create an account for a calendar sync on the phone
Synchronize the calendar
Delete the account
EXPECTED RESULT:
No reminders for ther deleted account
ACTUAL RESULT:
Reminders for the deleted account
ADDITIONAL INFORMATION:
(Please ALWAYS attach relevant data such as logs, screenshots, etc…)
Ok, thank you for the details. I’ll try to see if I can find an idea.
Normally here is the code path when deleting an account:
in Buteo, when the account is deleted, the plugin responsible for the sync is called and it’s cleanup() function is called.
the sync plugin cleanup should call a deleteNotebook() function from mKCal to cleanup the data.
the deleteNotebook() is listing all events related to the notebook and schedule them for deletion.
after all events have been deleted, this list of incidences is passed to a function called clearAlarms() in mKCal.
for each events, the timed daemon is contacted to clear the alarm related to this specific event.
That’s why I asked precisions : the cleanup function is in the sync plugin (here I cannot check, this is proprietary software), if an event is not in the calendar anymore, it should have been removed from the alarms also. So I need to figure out how events can be removed without associated alarm being removed also…
Another question : do you know if only some alarms remain (meaning that some have actually been removed) or globally all of them are still pending. To list alarms, use:
Interesting, thanks. One last question, maybe, do you notice a pattern on the remaining alarms ? In case could you post the output of the timedclient-qt5 -L command ? Or PM it to me ?
Thanks for reiterating it again here @phklrz. @pherjung did kindly pass the info on, but I didn’t see it stated publicly on the forum so thought I’d better double check.
Given this I’ve tagged it as “fixed”, but if it does recur, please do flag it up again and I’ll create an internal report about it.