EDS reverts alarm status immediately
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Ubuntu Clock App | Status tracked in Trunk | |||||
| Trunk |
Fix Released
|
High
|
Zsombor Egri | |||
| Ubuntu UI Toolkit |
Invalid
|
Undecided
|
Unassigned | |||
| qtorganizer5-eds (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | |||
Bug Description
The clock app provides switches to enable/disable individual alarms. However sometimes, I have noticed that on disabling an alarm, it immediately enables it again. Multiple tries to disable the alarm does not help. Again the key thing to remember here is that this does not happen everytime but only sometime. I have not found a reliable way to reproduce the issue. So you may have to do a bit of trial and error to confirm this bug.
Steps to reproduce:
1. Open clock app and navigate to alarm tab
2. Open toolbar and select "Add alarm"
3. Set any alarm (single or recurring)
4. Save the alarm
5. Attempt to set the alarm to disable by clicking the switch next to the new alarm
What happens sometimes:
The alarm is enabled again immediately by the system
What should happen
Since the user can toggle the alarm in the app, it is expected that the alarm can be turned off (so it is seen as disabled in the Upcoming settings menu tab)
Video showing the issue http://
Related branches
- Ubuntu Phone Apps Jenkins Bot: Approve (continuous-integration)
- Zsombor Egri (community): Approve
- Ubuntu Clock Developers: Pending requested
-
Diff: 55 lines (+27/-7)2 files modifiedapp/alarm/AlarmDelegate.qml (+23/-7)
debian/changelog (+4/-0)
| Changed in ubuntu-clock-app: | |
| milestone: | none → 1.6 |
| Renato Araujo Oliveira Filho (renatofilho) wrote | #1 |
| Nekhelesh Ramananthan (nik90) wrote | #2 |
| Changed in ubuntu-clock-app: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Renato Araujo Oliveira Filho (renatofilho) |
| description: | updated |
| Changed in ubuntu-clock-app: | |
| milestone: | 1.6 → 1.8 |
| tags: | added: alarms dogfooding-blocker |
| description: | updated |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in qtorganizer5-eds (Ubuntu): | |
| status: | New → Confirmed |
| Changed in ubuntu-clock-app: | |
| milestone: | 1.8 → backlog |
| Renato Araujo Oliveira Filho (renatofilho) wrote | #4 |
| Changed in qtorganizer5-eds (Ubuntu): | |
| status: | Confirmed → Invalid |
| Changed in ubuntu-clock-app: | |
| assignee: | Renato Araujo Oliveira Filho (renatofilho) → nobody |
| Changed in ubuntu-clock-app: | |
| milestone: | backlog → alarm-blockers |
| Changed in ubuntu-clock-app: | |
| milestone: | alarm-blockers → rtm |
| Changed in ubuntu-clock-app: | |
| milestone: | rtm → backlog |
| status: | Triaged → Won't Fix |
| Ubuntu Phone Apps Jenkins Bot (ubuntu-phone-apps-jenkins-bot) wrote | #5 |
| Changed in ubuntu-clock-app: | |
| status: | Won't Fix → Fix Committed |
| Changed in ubuntu-clock-app: | |
| status: | Fix Committed → Won't Fix |
| Changed in ubuntu-ui-toolkit: | |
| status: | New → Invalid |
could you isolate the bug in a small app?