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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283236
Title:
Alarms are triggered in UTC tz despite saving in local tz
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1283236/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
