FWIW, this also apparently makes it impossible to set an alarm for today if the current time is between midnight and the number of hours past UTC your time zone is.
So, I'm in UTC-6. It's 2am. I can't set an alarm to go off in 15 minutes (or any time before 6am), because it automatically sets the alarm for *tomorrow*. Even if I tell it to repeat every day of the week. -- You received this bug notification because you are a member of Unity API bugs, which is subscribed to Indicator Date and Time. 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: In Progress 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 -- Mailing list: https://launchpad.net/~unity-api-bugs Post to : unity-api-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~unity-api-bugs More help : https://help.launchpad.net/ListHelp
