dx-packages team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

To follow up on renato's comment #5... we could simply convert back from
UTC to localtime in indicator-datetime, but that will only work
correctly if you're running in the same timezone where the alarm was
created.

And in fact we're already making this mistake in the clock app:

  1. create & save a new wakeup alarm to kick at 6am m-f
  2. exit ubuntu-clock-app
  3. kill all evolution processes to ensure everything in its cache gets flushed
  4. change to another timezone
  5. restart ubuntu-clock-app
  6. result: the alarm no longer kicks at 6am

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1283236

Title:
  Alarms are triggered in UTC tz despite saving in local tz

Status in The Date and Time Indicator:
  In Progress
Status in Clock application for Ubuntu devices:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  Confirmed
Status in “qtorganizer5-eds” package in Ubuntu:
  Confirmed

Bug description:
  Setting an alarm in the local timezone is not respected by the system
  since the alarms is triggered in the equivalent UTC timezone.

  Mako build 200, 205

  Steps to reproduce: 
  1. Ensure that phone timezone is something other than UTC. For instance eastern tz (UTC-5)
  2. Set an alarm for 3:00 PM in the ubuntu clock app.
  3. Indicator shows a pending alarm for 3:00 PM
  4. Check a minute or so later, indicator shows an alarm pending for 8:00 PM

  What happens:
  The alarm does not go off at 3:00 PM. Instead it triggers at 8:00 PM

  What should happen:
  The alarm is triggered at 3:00 PM

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1283236/+subscriptions