dx-packages team mailing list archive

[Pat McGowan <pat.mcgowan@xxxxxxxxxxxxx>]

It seems some layer is interpreting the alarm time being requested as
UTC instead of the local timezone, thereby scheduling it 5 hrs too far
ahead.  It looks like clock and the alarm api expect localtime although
this is not explicit in the API doc.

We should ensure that timezone changes are reacted to properly for saved
alarms. Perhaps all alarms should be saved in UTC and converted as
appropriate.

** Changed in: ubuntu-clock-app
     Assignee: (unassigned) => Nekhelesh Ramananthan (nik90)

-- 
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:
  Alarm is shown with an incorrect time and does not trigger

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

Bug description:
  Mako build 200
  Phone is in eastern time zone (UTC - 5) at 2:55pm
  Set an alarm for 3:00 pm
  Indicator shows a pending alarm for 3:00 pm
  Check a minute or so later, indicator shows an alarm pending for 8:00pm
  The alarm does not go off at 3:00 pm.

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