Stopwatch is not working correctly after change timezone during runtime
Bug #1493358 reported by
Bartosz Kosiorek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
Unassigned | ||
Ubuntu Clock App |
Fix Released
|
Critical
|
Bartosz Kosiorek |
Bug Description
Stopwatch is not working correctly after change timezone during runtime.
Steps to reproduce:
1. Run clock
2. Start stopwatch
3. Get Clock into background
4. Change timezone
5. Switch to stopwatch
Currently:
- Stopwatch is showing wrong time
Expected:
- Stopwatch should show correct time
Related branches
lp:~gang65/ubuntu-clock-app/ubuntu-clock-stopwatch-runtime-timezone-fix
- Bartosz Kosiorek: Approve
- Nekhelesh Ramananthan: Approve (testing and code review.)
- Ubuntu Phone Apps Jenkins Bot: Approve (continuous-integration)
- Victor Thompson: Needs Fixing
- Michael Zanetti: Pending requested
-
Diff: 621 lines (+224/-116)14 files modifiedREADME.autopilot (+1/-1)
README.developers (+2/-2)
README.unittest (+3/-3)
app/MainPage.qml (+3/-10)
app/components/HeaderNavigation.qml (+1/-1)
app/stopwatch/LapListView.qml (+1/-1)
app/stopwatch/StopwatchPage.qml (+18/-71)
backend/CMakeLists.txt (+1/-1)
backend/modules/Stopwatch/backend.cpp (+2/-2)
backend/modules/Stopwatch/engine.cpp (+113/-10)
backend/modules/Stopwatch/engine.h (+56/-14)
debian/changelog (+1/-0)
tests/manual/2014.com.ubuntu.clock:clock-tests/jobs/stopwatch.pxu (+21/-0)
tests/manual/2014.com.ubuntu.clock:clock-tests/whitelists/clock-app-stopwatch.whitelist (+1/-0)
Changed in ubuntu-clock-app: | |
status: | Triaged → In Progress |
assignee: | nobody → Bartosz Kosiorek (gang65) |
Changed in ubuntu-clock-app: | |
milestone: | none → 3.6 |
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
milestone: | none → ww46-2015 |
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.
Wasn't this fixed under lp:1491024? Why was this not situation not tested under that fix?