** Changed in: ubuntu-ui-toolkit
Status: Fix Committed = Fix Released
--
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
** Changed in: ubuntu-clock-app
Milestone: alarm-blockers = rtm
--
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
** 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 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
Just confirming this works for me now, on image utopic 18.
--
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
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
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 Unity
** Tags added: r276
--
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
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 Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/1283236
Title:
** 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 Unity API
bugs, which is subscribed to Indicator Date and Time.
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/alarm-date-fix
--
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
** Changed in: ubuntu-ui-toolkit
Status: New = In Progress
--
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
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)
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
** Branch linked: lp:~charlesk/indicator-datetime/lp-1283236
--
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
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
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
** Branch linked: lp:~renatofilho/qtorganizer5-eds/fix-1283236
--
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
** Changed in: qtorganizer5-eds (Ubuntu)
Assignee: (unassigned) = Renato Araujo Oliveira Filho (renatofilho)
--
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:
** Changed in: qtorganizer5-eds (Ubuntu)
Importance: Undecided = High
--
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
** Changed in: indicator-datetime
Assignee: (unassigned) = Charles Kerr (charlesk)
--
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
** Changed in: indicator-datetime
Status: New = Confirmed
--
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
@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());
** 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 Unity API
bugs, which is subscribed to Indicator Date and Time.
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 Unity API
bugs, which is subscribed to Indicator Date and Time.
** Project changed: qtorganizer5-eds = qtorganizer5-eds (Ubuntu)
--
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
26 matches
Mail list logo
