** Changed in: ubuntu-ui-toolkit
Status: Fix Committed => Fix Released
--
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
** Changed in: ubuntu-clock-app
Milestone: alarm-blockers => rtm
--
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
** Changed in: qtorganizer5-eds (Ubuntu)
Status: Confirmed => Fix Released
--
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
** Changed in: indicator-datetime
Status: In Progress => Fix Released
** Changed in: indicator-datetime (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: indicator-datetime (Ubuntu)
Importance: Undecided => High
** Changed in: indicator-datetime (Ubuntu)
Assignee: (
** Changed in: ubuntu-clock-app
Status: Invalid => Fix Released
--
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 mana
** Changed in: ubuntu-clock-app
Milestone: 1.8 => alarm-blockers
--
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
Just confirming this works for me now, on image utopic 18.
--
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 notificat
This bug was fixed in the package ubuntu-ui-toolkit -
0.1.46+14.10.20140502.6-0ubuntu1
---
ubuntu-ui-toolkit (0.1.46+14.10.20140502.6-0ubuntu1) utopic; urgency=low
[ Tarmac ]
* [ Zoltán Balogh] * Skip tests only for powerpc [ Christian Dywan
] * Use locale format specifi
Fix committed into lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/staging at
revision 1010, scheduled for release in ubuntu-ui-toolkit, milestone
Unknown
** Changed in: ubuntu-ui-toolkit
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
B
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-ui-toolkit (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
T
Yes, Charles, I'm giving the date to qtorganizer-eds transformed into
UTC (i.e. 3pm Local time === 3pm UTC). Now, all tasks.ics entries are in
UTC. But I guess we agreed that it is OK to have that. If not, eds
plugin must do sthing with the time.
--
You received this bug notification because you
Zsombor, the patch you're working on generates tasks.ics entries like
the one described in comment #10, right?
--
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 UT
** Tags added: r276
--
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
** Changed in: ubuntu-clock-app
Status: Confirmed => Invalid
** Changed in: ubuntu-clock-app
Assignee: Nekhelesh Ramananthan (nik90) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
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 th
** Tags added: r263
--
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
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/alarm-date-fix
--
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 notifi
** Changed in: ubuntu-ui-toolkit
Status: New => In Progress
--
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 n
Zsombor, I think so this is good enough for now, since qtorganizer5-eds
currently generates all its icaltimes as floating (because of the use of
with icaltime_from_timet()).
Given more time, it would be nicer to handle both floating and non-
floating times there. But since the only current user is
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Zsombor, could you expand on what "transform (not convert)" means here?
Ideally we would want alarms to all be floating times; ie, an alarm set
to go off on Feb 28 at 6am would be "DTSTART:20140228T06" with no
trailing zulu on the timestamp, and with no TZID parameter in the entry.
--
You re
We just agreed with renato that SDK Alarms will transform (not convert)
the alarm time into UTC value, and set them as alarm values. So the fix
will come from SDK.
** Also affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-ui-toolkit (Ubuntu)
To follow up on renato's comment #5... we could simply convert back from
UTC to localtime in indicator-datetime, but that will only work
correctly if you're running in the same timezone where the alarm was
created.
And in fact we're already making this mistake in the clock app:
1. create & save
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 F
** Branch linked: lp:~charlesk/indicator-datetime/lp-1283236
--
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 notific
Yep, I agree with Renato -- these are being saved in tasks.ics as
floating times, ie, localtime.
I think this is a datetime bug rather than something in qtorganizer5-eds
or ubuntu-ui-toolkit.
** Changed in: indicator-datetime
Status: Confirmed => In Progress
** Changed in: indicator-datet
** Branch linked: lp:~renatofilho/qtorganizer5-eds/fix-1283236
--
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 notif
@Charles, I am saving the event time in UTC formart using:
ECalComponentDateTime *dt = g_new0(ECalComponentDateTime, 1);
dt->value = g_new0(struct icaltimetype, 1);
*dt->value = icaltime_from_timet(etr.startDateTime().toTime_t(),
etr.isAllDay());
e_cal_component_se
** Changed in: indicator-datetime
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
Title:
Alarms are triggered in UTC tz despite saving in local tz
To manage no
** Changed in: indicator-datetime
Assignee: (unassigned) => Charles Kerr (charlesk)
--
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
** Changed in: qtorganizer5-eds (Ubuntu)
Importance: Undecided => High
--
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 m
** Changed in: qtorganizer5-eds (Ubuntu)
Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)
--
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 i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtorganizer5-eds (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
Ti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtorganizer5-eds (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
Ti
** Also affects: qtorganizer5-eds
Importance: Undecided
Status: New
--
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
** Project changed: qtorganizer5-eds => qtorganizer5-eds (Ubuntu)
--
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 no
** Description changed:
- Mako build 200
- Phone is in eastern time zone (UTC - 5) at 2:55pm
- Set an alarm for 3:00 pm
- Indicator shows a pending alarm for 3:00 pm
- Check a minute or so later, indicator shows an alarm pending for 8:00pm
- The alarm does not go off at 3:00 pm.
+ Setting an alarm
** Summary changed:
- Alarm is shown with an incorrect time and does not trigger
+ Alarms are triggered in UTC tz despite saving in local tz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283236
Titl
38 matches
Mail list logo
