desktop-packages team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1465806

Title:
  Alarms not shown in indicator datetime after upgrade to ota4

Status in the base for Ubuntu mobile products:
  New
Status in evolution-data-server package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Flash image 22 from stable
  2. Set a one time alarm and a recurring alarm
  3. Update to 23

  EXPECTED:
  Alarms should be up and running as expected

  ACTUAL:
  Alarms are not shown in the datetime indicator but show up as active in and available in the clock.  Because the indicator is in control of the alarm trigger the alarm never goes off.

  TEMPORARY WORK AROUND:
  Disable and enable all your alarms and then they work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1465806/+subscriptions