gnome-calendar crashed with SIGSEGV (second error)

[Mac]

The error has occurred two times. The first on entering the last set of account details to populate the calendar and the second was encountered on viewing weekly calendar info and then closing the calendar.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-calendar 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Mar 30 19:24:29 2017
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2017-03-24 (5 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x55685877c195 <get_start_of_week+37>: mov 0x0(%rbp),%r12d
 PC (0x55685877c195) ok
 source "0x0(%rbp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 get_start_of_week ()
 gcal_week_header_add_event ()
 ?? ()
 ?? ()
 e_cal_data_model_subscribe ()
Title: gnome-calendar crashed with SIGSEGV in get_start_of_week()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1666205, 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.