** Changed in: ubuntu-clock-app
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/1283859
Title:
Updated recurring alarm values
** 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/1283859
Title:
Updated recurring alarm values are not reflected in the indicator
** 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/1283859
Title:
Updated recurring alarm values are not reflected in the indicator
** Changed in: ubuntu-clock-app
Milestone: 2.0 = alarm-blockers
** Changed in: ubuntu-clock-app
Importance: High = Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283859
Title:
** Changed in: ubuntu-clock-app
Status: Confirmed = Invalid
** Changed in: ubuntu-ui-toolkit
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283859
Title:
** Branch linked: lp:ubuntu/trusty-proposed/qtorganizer5-eds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283859
Title:
Updated recurring alarm values are not reflected in the indicator
until
This bug was fixed in the package qtorganizer5-eds -
0.1.1+14.04.20140415.1-0ubuntu1
---
qtorganizer5-eds (0.1.1+14.04.20140415.1-0ubuntu1) trusty; urgency=low
[ Renato Araujo Oliveira Filho ]
* Optimize eventid parse, and avoid memory leak. (LP: #1306112)
* Used alarm
** Changed in: qtorganizer5-eds (Ubuntu)
Status: Confirmed = In Progress
** 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
Renato, yes! lp:~renatofilho/qtorganizer5-eds/fix-1283859 fixes this for
the test I described in comments #5 and #6 :D
** Changed in: indicator-datetime
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@nick90, @charles, could you test my branch?
Looks like the problem is related with the update mode used during the event
save.
** Branch linked: lp:~renatofilho/qtorganizer5-eds/fix-1283859
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ubuntu-clock-app
Milestone: 1.8 = 2.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283859
Title:
Updated recurring alarm values are not reflected in the indicator
until phone
Still present in r276.
I'm testing this out on r276 this morning and am getting confusing
results. At first I thought it was an indicator-datetime caching bug,
because the modified alarms are being successfully saved to tasks.ics.
However, even if I stop and restart indicator-datetime, the new
Steps I used to test this:
1. ssh'ed into the phablet
2. built lp:~charlesk/indicator-datetime/log-instances-to-terminal,
which is stock indicator-datetime plus this console message:
http://bazaar.launchpad.net/~charlesk/indicator-datetime/log-instances-
to-terminal/revision/337
3. $ stop
** Branch unlinked: lp:~zsombi/ubuntu-ui-toolkit/alarm-fetch-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283859
Title:
Updated recurring alarm values are not reflected in the indicator
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/alarm-fetch-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283859
Title:
Updated recurring alarm values are not reflected in the indicator
until
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/1283859
** Description changed:
Mako 205
Steps to reproduce:
1. Create a recurring alarm and save it
2. Select the saved alarm to go to edit mode
- 3. Change the time or day of the alarm
+ 3. Change the time, day of the alarm or status of the alarm.
4. Hit save
What happens:
The alarm
Ahh, sorry, my comments are on the wrong bug :) Let me check if I can
get rid of the dueDate() and rely only on startDate()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283859
Title:
Updated
Okay, after a bit of digging I think what we need to do is remove the
event.setDueDateTime(alarm.date); line from ubuntu-ui-toolkit's
AlarmsAdapter::organizerEventFromAlarmData().
Here's an abbreviated example of a vtodo written to tasks.ics by ubuntu-
clock-app -- ubuntu-ui-toolkit --
Alarms fetched in Alarms API are getting their date from the due date,
which is the due date of the next occurrence. The question is whether I
get a proper date at fetch time if I do not set the due date for the
original event. Or is the due date for the individual occurrences set
independently
** Also affects: indicator-datetime
Importance: Undecided
Status: New
** Also affects: qtorganizer5-eds
Importance: Undecided
Status: New
** Project changed: qtorganizer5-eds = qtorganizer5-eds (Ubuntu)
--
You received this bug notification because you are a member of
21 matches
Mail list logo
