dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #09850
[Bug 1283236] Re: Alarms are triggered in UTC tz despite saving in local tz
I meant transform the local hour into exactly same UTC time (i.e. 3:00am
UTC+2 onto 3:00am UTC). Would this be good enough? Or would this still
contain TZ info?
--
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 Ubuntu UI Toolkit:
New
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
References