gnome-clocks crashed with SIGSEGV in g_date_time_to_timezone()

StacktraceTop:
 g_date_time_to_timezone () from /tmp/apport_sandbox_hd9rilqt/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 clocks_world_item_calculate_riseset (self=0x561a2d9f6620) at src/25a6634@@gnome-clocks@exe/world.c:1341
 clocks_world_item_real_tick (self=0x561a2d9f6620) at src/25a6634@@gnome-clocks@exe/world.c:2068
 g_closure_invoke () from /tmp/apport_sandbox_hd9rilqt/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6400.1
 signal_emit_unlocked_R () from /tmp/apport_sandbox_hd9rilqt/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6400.1

Thank you for submitting this SRU Seb! I will accept it, but I must say that I am not a great fan of multi-patches patch files as you provided, it makes reviewing the changes harder. And dpkg-source doesn't like it as well: "diff 'gnome-clocks-3.36.0/debian/patches/git_twilight_segfault.patch' patches file gnome-clocks-3.36.0/src/twilight.c more than once".

Please be sure to either provide a single patch with all the needed patch-changes or separate patch files per patch-set next time.

Hello Fabio, or anyone else affected,

Accepted gnome-clocks into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-clocks/3.36.0-1ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hi, I installed the proposed version from here: http://launchpadlibrarian.net/478194856/gnome-clocks_3.36.0-1ubuntu0.1_amd64.deb

Everything works for me.

I tried Helsinki, Stockholm and Cagliari time zones, set a timer, tried stopwatch and timer. No issues.

Also, timezones correctly appear in the Shell, when clicking on the time.

http://launchpadlibrarian.net/478194856/gnome-clocks_3.36.0-1ubuntu0.1_amd64.deb fixes this bug for me. Tested world clock, timer and stop watch.

http://launchpadlibrarian.net/478194856/gnome-clocks_3.36.0-1ubuntu0.1_amd64.deb corrected for me too. He reopened the application normally.

Yes! Fixes this bug for me too.

https://launchpad.net/ubuntu/+source/gnome-clocks/3.36.0-2

This bug was fixed in the package gnome-clocks - 3.36.0-1ubuntu0.1

---------------
gnome-clocks (3.36.0-1ubuntu0.1) focal; urgency=medium

  * debian/patches/git_twilight_segfault.patch:
    - backport a segfault fix from upstream in case where the twilight
      start can't be determined (lp: #1873077)

 -- Sebastien Bacher <email address hidden> Tue, 28 Apr 2020 11:31:23 +0200

The verification of the Stable Release Update for gnome-clocks has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

There's a possible regression, please see bug 1878361.

Hi, `gnome-clocks --version`` shows Clocks 3.36.0 and I'm still experiencing segfault. I think that is the latest version with the fix that is working for some people above?