[Vivid][Regression] Alarms times are incorrectly saved when editing an alarm
Bug #1401883 reported by
Nekhelesh Ramananthan
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-ui-toolkit (Ubuntu) |
Fix Released
|
Critical
|
Zsombor Egri | ||
Vivid |
New
|
Undecided
|
Unassigned |
Bug Description
In Vivid, the clock app cannot edit alarm correctly since the alarm times chosen is not taken into account due to timezone management by the Ubuntu SDK Alarms Backend.
Steps to reproduce:
1. In the latest vivid images, open the clock app
2. Create a new alarm to ring in the next few minutes and save it.
3. Edit the alarm and change the time.
4. save the alarm
What happens:
The alarm is not updated with the new alarm time chosen in step 3
What should happen
The newly changed alarm time should be used.
Related branches
lp:~zsombi/ubuntu-ui-toolkit/alarm-regression-fix
- PS Jenkins bot: Approve (continuous-integration)
- Cris Dywan: Pending requested
-
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)
description: | updated |
summary: |
- [Vivid][Regression] Alarms times is incorrectly saved when editing an + [Vivid][Regression] Alarms times are incorrectly saved when editing an alarm |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
assignee: | nobody → Zsombor Egri (zsombi) |
importance: | Undecided → High |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
importance: | High → Critical |
tags: | added: qa-promotion touch |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.