gnome-calendar crashed with SIGSEGV in g_source_get_ready_time()

[Cliff Carson]

This crash show up right after booting up the system. Unknown what caused it.

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: gnome-calendar 3.38.1-2
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu55
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 9 21:18:18 2020
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2020-12-05 (4 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201205)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fc6ae4351dd <g_source_get_ready_time+13>: mov 0x18(%rdi),%eax
 PC (0x7fc6ae4351dd) ok
 source "0x18(%rdi)" (0x6d7856a000000020) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 g_source_get_ready_time () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gcal_timer_is_running ()
 ()
 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-calendar crashed with SIGSEGV in g_source_get_ready_time()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1869068, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.