Repeating alarms appear disabled in clock app after it went off once
Bug #1411171 reported by
Jean-Baptiste Lallement
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Unassigned | ||
Ubuntu Clock App |
Fix Released
|
High
|
Charles Kerr | ||
indicator-datetime (Ubuntu) |
Fix Released
|
High
|
Charles Kerr | ||
indicator-datetime (Ubuntu RTM) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
krillin #198
Repeating alarm is disabled after the first time it goes off.
Test Case:
1. Setup a repeating alarm (everyday from Monday to Friday for example) and enable it
2. Close the clock app
3. Wait until it goes off
4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next occurrence)
5. Resume the device
6. Launch the clock app
7. Go the alarms and verify the status of the alarm
Actual Result:
The alarm is disabled but it shows in the indicator.
The next and next-next occurrences of the alarm are scheduled correctly.
Expected Result
Alarm is still enabled.
Related branches
lp://qastaging/~charlesk/indicator-datetime/lp-1411171-strengthen-recurrence-rule-test-rtm-14.09
- dobey (community): Approve
-
Diff: 34 lines (+11/-2)2 files modifiedsrc/engine-eds.cpp (+5/-2)
tests/manual (+6/-0)
lp://qastaging/~charlesk/indicator-datetime/lp-1411171-strengthen-recurrence-rule-test
- Antti Kaijanmäki (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- dobey (community): Approve
-
Diff: 46 lines (+12/-2)3 files modifiedsrc/engine-eds.cpp (+5/-2)
src/main.cpp (+1/-0)
tests/manual (+6/-0)
Changed in ubuntu-clock-app: | |
status: | New → Confirmed |
description: | updated |
summary: |
- Repeating alarm disabled after it went off once + Repeating alarms are disabled after it went off once |
Changed in ubuntu-clock-app: | |
milestone: | none → ota-1 |
tags: | added: alarm |
summary: |
- Repeating alarms are disabled after it went off once + Repeating alarms appear disabled in clock app after it went off once |
Changed in ubuntu-clock-app: | |
importance: | Undecided → High |
Changed in indicator-datetime (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
assignee: | nobody → Charles Kerr (charlesk) |
Changed in ubuntu-clock-app: | |
assignee: | nobody → Charles Kerr (charlesk) |
Changed in canonical-devices-system-image: | |
importance: | Undecided → High |
milestone: | none → ww05-2015 |
status: | New → Confirmed |
tags: | added: lt-category-visible |
tags: | added: lt-blocker |
Changed in canonical-devices-system-image: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
STEPS TO TEST CLOCK APP OVER EDS:
1. Set a repeatable alarm as above
2. Mock the day change with the following (Supposing alarm 1 was Monday 09:20)
adb shell
sudo date -s "Tue Jan 20 09:19:00 2015"
<change the date as appropriate>
3. You will note that the alarm still goes off so eds has the data correctly in place only the alarms page displays that the alarm is disabled.