Strange behaviour of alarms after changing timezone
Bug #1495883 reported by
Bartosz Kosiorek
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Fix Released
|
Medium
|
Unassigned | ||
| Ubuntu Clock App |
Fix Released
|
Medium
|
Bartosz Kosiorek | ||
Bug Description
With current implementation of alarms, alarms is saved as whole Date and Time (eg. 2015.09.015 16:00).
It is causing that after changing timezone, the alarm is still enabled, but it is already passed.
Steps to reproduce:
1. Let's say that we have date 2015.09.15 23:00
2. Create new alarm and set it to: 2015.09.15 23:30
3. Change timezone +2, we have date 2015.09.16 01:00
Currently:
- Alarm is still active but it will not ring as it is in the past
Expected:
- Alarm should still ring at 23.30, no matter in which timezone
Implementation proposal:
To resolve that issue we should save hour and minute of alarm, and information if alarm is enabled.
We shouldn't save exact date of alarm.
Related branches
lp:~gang65/ubuntu-clock-app/ubuntu-clock-app-disabled-alarm-fix
- Ubuntu Phone Apps Jenkins Bot: Needs Fixing (continuous-integration)
- Nekhelesh Ramananthan: Approve
- Victor Thompson: Needs Fixing
- Bartosz Kosiorek: Approve
-
Diff: 181 lines (+25/-25)3 files modifiedapp/alarm/AlarmDelegate.qml (+3/-4)
debian/changelog (+1/-0)
po/com.ubuntu.clock.pot (+21/-21)
| Changed in ubuntu-clock-app: | |
| milestone: | none → 3.6 |
Revision history for this message
| Victor Thompson (vthompson) wrote | #1 |
| Changed in ubuntu-clock-app: | |
| importance: | Critical → Medium |
| Changed in ubuntu-clock-app: | |
| milestone: | 3.6 → 3.7 |
| Changed in ubuntu-clock-app: | |
| milestone: | 3.7 → 3.6 |
| assignee: | nobody → Bartosz Kosiorek (gang65) |
| status: | Triaged → In Progress |
| Changed in canonical-devices-system-image: | |
| importance: | Undecided → Medium |
| milestone: | none → ww46-2015 |
| status: | New → Confirmed |
| Changed in ubuntu-clock-app: | |
| status: | In Progress → Fix Committed |
| Changed in ubuntu-clock-app: | |
| status: | Fix Committed → Fix Released |
| Changed in canonical-devices-system-image: | |
| status: | Confirmed → Fix Committed |
| Changed in canonical-devices-system-image: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Is this a duplicate of lp:1472525? Or is that a different error?