** 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/1308193
Title:
Upcoming recurring alarms on wrong day
To manage notifications
Marking as fixed based on personal testing and the above comments.
** Changed in: indicator-datetime (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: ubuntu-clock-app (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member
Yes, this seems working in the latest image #22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308193
Title:
Upcoming recurring alarms on wrong day
To manage notifications about this bug go to:
This appeared fixed during my testing as well on image #24.
** Changed in: ubuntu-clock-app
Assignee: Nekhelesh Ramananthan (nik90) = Zsombor Egri (zsombi)
** Changed in: ubuntu-clock-app
Status: Confirmed = Fix Released
--
You received this bug notification because you are a
** Changed in: ubuntu-clock-app
Milestone: backlog = 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/1308193
Title:
Upcoming recurring alarms on wrong day
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-datetime (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/1308193
** Changed in: indicator-datetime (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308193
Title:
Upcoming recurring alarms on wrong day
To manage notifications
** Changed in: indicator-datetime (Ubuntu)
Assignee: (unassigned) = Charles Kerr (charlesk)
** Changed in: indicator-datetime (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-datetime (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/1308193
Looks like this might be a clock-app bug rather than an indicator-
datetime one. Here's what gets saved in EDS' backend. Note that today is
April 15 but the alarm's start date is stored as April 21
(DTSTART:20140421T06)
I'm able to reproduce this issue on r297, right after a full reflash.
Just create a morning alarm for M-F, and even though today is Tuesday,
indicator-datetime shows the upcoming time as Monday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This value is being set in qtorganizer5-eds by
QOrganizerEDSEngine::parseTodoStartTime(), which gets the value from a
call to a QOrganizerTodoTime.startDateTime().
Looks like the QOrganizerTodo gets set in ubuntu-ui-
toolkit/modules/Ubuntu/Components/plugin/adapters/alarmsadapter_organizer.cpp
I think I may have found the bug. On reading the SDK Alarms API
documentation, it specifies that if the daysOfTheWeek are specified,
then it will strive to trigger the alarms on that day. Let me illustrate
an example here to explain.
Assume that the current date and time is Monday 15th April
13 matches
Mail list logo
