gnome-calendar crashed with SIGSEGV in g_str_equal()

[Sven.Frings]

Ubuntu-Budgie 18.04 beta 1

Software Version gnome-calendar:
  Installiert: 3.28.0-1
  Installationskandidat: 3.28.0-1
  Versionstabelle:
 *** 3.28.0-1 500

Tried to open gnome calendar program when it´s crashed

What i expect ? That gneome-calendar open

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sun Mar 25 12:07:33 2018
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2018-03-11 (13 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f7037a53102 <__strcmp_sse2_unaligned+658>: movzbl (%rdi,%rdx,1),%eax
 PC (0x7f7037a53102) ok
 source "(%rdi,%rdx,1)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 g_str_equal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__POINTERv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-calendar crashed with SIGSEGV in g_str_equal()
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 #1755960, 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.