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 react
** Changed in: ubuntu-clock-app
Importance: Undecided => High
** Changed in: ubuntu-clock-app
Status: New => Confirmed
** Changed in: ubuntu-clock-app
Milestone: None => 1.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-datetime (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283236