dx-packages team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

Actually my last comment was only half right. indicator-datetime does
have a bug that doesn't set the fallback timezone for EDS to use when
loading events, but there is a bigger problem in qtorganizer5-eds.

So, I'm in UTC-6 and just used ubuntu-clock-app to create a one-time
alarm to kick on Wed Feb 27th at 9 PM. What gets saved to tasks.ics is
this:

    DTSTART:20140227T030000
    DUE:20140227T030000
    SUMMARY:Alarm

Note the lack of timezone information. That makes this a "floating"
time, meaning that the alarm will kick at that specified time regardless
of timezone. This is a Good Thing, since that means our M-F 6am wakeup
alarms will kick at 6am even if we travel to a different timezone.

So that's the good news. The bad news, the kick time is floating at
2014-02-27 03:00:00. That means EDS being sent a VTODO that kicks at 3am
no matter what timezone it's in.... and that's why indicator-datetime is
showing what it's showing.

-- 
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