[Vivid][Regression]Cannot change alarm switch status (enable/disable alarms)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Canonical System Image |
High
|
Zoltan Balogh | ||
| | Ubuntu Clock App |
High
|
Zsombor Egri | ||
Bug Description
ubuntu 15.04 (all releases) on mako
App-Version: 3.3.192
1st:
What I expected:
When I switch an alert off, it should be off until I turn it on.
What happens instead:
When I switch an alert off and wait a bit (5-10 sec), then goes the switch on.
2nd:
What I expected:
When I change an alert (alert-time or days-of-week, when it shall alert) and go back, it should save then changes.
What happens instead:
The change wasn't saved. So the time/the days, when/on which the alert rings, is the old one.
Related branches
- PS Jenkins bot: Approve (continuous-integration) on 2015-02-26
- Christian Dywan: Pending requested 2015-02-26
-
Diff: 627 lines (+185/-91)10 files modifiedmodules/Ubuntu/Components/plugin/adapters/alarmsadapter_organizer.cpp (+19/-15)
modules/Ubuntu/Components/plugin/adapters/alarmsadapter_p.h (+33/-12)
modules/Ubuntu/Components/plugin/alarmmanager_p.cpp (+7/-8)
modules/Ubuntu/Components/plugin/alarmmanager_p.h (+1/-1)
modules/Ubuntu/Components/plugin/alarmmanager_p_p.h (+1/-3)
modules/Ubuntu/Components/plugin/ucalarm.cpp (+2/-0)
modules/Ubuntu/Components/plugin/ucalarmmodel.cpp (+3/-2)
tests/resources/alarm/AlarmDays.qml (+4/-4)
tests/resources/alarm/Alarms.qml (+55/-43)
tests/unit_x11/tst_components/tst_alarms.qml (+60/-3)
| summary: |
- Cannot change alerts + [Vivid][Regression]Cannot change alerts |
| Changed in ubuntu-clock-app: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| summary: |
- [Vivid][Regression]Cannot change alerts + [Vivid][Regression]Cannot change alarm switch status (enable/disable + alarms) |
| Nekhelesh Ramananthan (nik90) wrote : | #1 |
| tags: |
added: alarm qa-promotion touch removed: alert clock not save |
| Changed in ubuntu-clock-app: | |
| status: | Confirmed → Invalid |
| importance: | High → Undecided |
| Marcel Hörz (marzel) wrote : | #2 |
Nothing happens in the last two updates.
What work:
- Changing repeat-options of an alert.
What doesn't work:
- Switching on/off alert
- Changing time of alert
Device: malo (NEXUS 4)
System: Ubuntu 15.04 r121
| Nekhelesh Ramananthan (nik90) wrote : | #3 |
@Marcel, indeed which is why the bug has been marked as "Fix Committed" and not "Fix released" :) ... It still needs to land on the daily devel images which should happen soon.
| Changed in canonical-devices-system-image: | |
| importance: | Undecided → High |
| milestone: | none → ww13-2015 |
| status: | New → Fix Committed |
| assignee: | nobody → Zoltan Balogh (bzoltan) |
| Changed in canonical-devices-system-image: | |
| status: | Fix Committed → Fix Released |
| Changed in ubuntu-clock-app: | |
| milestone: | none → 3.4 |
| importance: | Undecided → High |
| status: | Invalid → Fix Released |
| assignee: | nobody → Zsombor Egri (zsombi) |
| no longer affects: | ubuntu-clock-app/vivid-15.04 |
@Zsombor and Victor, This bug was indeed caused by the same regression in bug #1401883. On installing the latest SDK toolkit staging 1424 rev on Nexus 4, I am able to enable/disable alarms successfully. Thnx Zsombor for the fix. As such I am marking this bug fix committed.
On a side note, I have also noticed that the clock app now crashes often when pressing on the "Add new alarm" button. But I will investigate more on that and create a new bug to track that issue.