Comment 4 for bug 1465806

I see what the problem is -- the alarms created by ubuntu-clock-app in image 22 have valarms that are missing the required 'trigger' property. This works for alarms created by qtorganizer5-eds after the fix for bug #1440878 landed -- which is why disabling and then re-enabling the alarms as davmor2 works as a workaround -- but that still leaves the question of how to handle these triggerless alarms without requiring a workaround.

Until 13.10.0+15.04.20150521-0ubuntu1, indicator-datetime /pretended/ that x-canonical-alarm entries had a trigger even if they didn't. That's no longer possible because we're now querying EDS for alarms based on the trigger, which was necessary to fix bug #1456281.

Probably the safest fix here is for indicator-datetime to ask EDS on startup for all the x-canonical-alarm components, then walk through them looking for valarms missing a trigger, insert the missing trigger, and save the corrected entry back to EDS.