** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1858857
Title: gnome-calendar: Hits assert when timezone set to Etc/UTC Status in gnome-calendar package in Ubuntu: In Progress Status in gnome-calendar source package in Focal: In Progress Bug description: [Impact] When the system timezone is set to Etc/UTC, most notably in the 20.04 Live CD environment, gnome-calendar fails to start, as it hits an assert. ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL) Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL) Aborted (core dumped) This is reproducible in focal with: gnome-calendar 3.34.2-1build1 This is NOT reproducible in eoan with: gnome-calendar 3.34.2-1 More seriously, this bug is triggered when a user presses the Super key in the Live CD test environment and searches for an application, as dbus will attempt to start the gnome-calendar service, and gnome- calendar will crash due to this bug. [Test Case] Change system timezone to Etc/UTC and attempt to launch gnome- calendar: ubuntu@ubuntu:/var/log$ sudo timedatectl set-timezone Etc/UTC ubuntu@ubuntu:/var/log$ timedatectl Local time: Tue 2020-02-18 02:49:21 UTC Universal time: Tue 2020-02-18 02:49:21 UTC RTC time: Tue 2020-02-18 02:49:22 Time zone: Etc/UTC (UTC, +0000) System clock synchronized: yes NTP service: active RTC in local TZ: no ubuntu@ubuntu:/var/log$ gnome-calendar ** ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL) Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL) Aborted (core dumped) [Regression Potential] The risk of regression is low due to the assert being removed and replaced with a default to UTC time if the previous timezone pointer is NULL. This is also only going to the focal development release, where any impact to real users will be low. [Other Information] There is an upstream issue open: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/485 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1858857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp