[SRU] Update gnome-clocks to 3.36.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-clocks (Debian) |
Fix Released
|
Unknown
|
|||
gnome-clocks (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
gnome-clocks 3.36.2 is a bug-fix release as part of GNOME 3.36.
https:/
It fixes two crashes related to handling world clocks, fixes the timer start button, fixes spamming the log with criticals, and fixes the stopwatch view not being scrollable to the bottom.
World: Handle impossible places
Timer: Fix signal for updating the duration
[Test case]
- Make sure all the functions work, adding world clocks, alarm, stopwatch and timer.
- Make sure that the timer start button is now enabled after entering minutes and/or seconds via keyboard or clicking on the plus and minus buttons.
- Start a stopwatch then add many laps until the view becomes scrollable and it can be scrolled to the bottom. Also clearing the stopwatch view should be smooth now.
[Regression potential]
• libcanberra is added to the flatpak .json because it was removed from the GNOME SDK. This is required for building the flatpak and does not affect running the application.
• Two crashes are fixed by adding more explicit casts and null checks in many places, and enabling the vala (experimental) null checker. The regression could be that the package doesn’t build any more, and/or the application loses functionality. However, it builds fine in my PPA for all architectures in Focal, and all functionalities run well.
https:/
• A fix is applied to the world clocks by handling impossible places to fix a crash and avoid spamming the log with criticals.
https:/
• A fix is applied to improve the handling of zones where twilight times can’t be calculated. This helps to fix the same bug mentioned above. The regression potential is the same as above.
https:/
• The timer start button was not enabled after entering minutes and/or seconds via keyboard (and changing focus via the tab key). This is now fixed.
https:/
• There was a theme parsing error. This is fixed now by ignoring the not-found resources.
https:/
• The stopwatch view was not scrollable to the bottom when many laps were added to the stopwatch view, and there was an animation glitch when clearing the view. This is now fixed.
https:/
• Version 3.36.2 has been in Groovy since June 2020 without bugs.
[Other]
gnome-clocks 3.36.2 has been successfully built as a no-change backport from Groovy to Focal in my PPA:
-------
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-clocks 3.36.0-1ubuntu0.1
ProcVersionSign
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Thu May 21 12:06:51 2020
InstallationDate: Installed on 2020-04-26 (24 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-clocks
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in gnome-clocks (Debian): | |
status: | Unknown → New |
Changed in gnome-clocks (Debian): | |
status: | New → Fix Released |
description: | updated |
Changed in gnome-clocks (Ubuntu): | |
status: | Incomplete → Confirmed |
Please SRU gnome-clocks 3.36.2 to Focal.