Description of problem:
I was restoring Evolution from a backup (File -> Restore Evolution Data…) when ABRT notified me that Gnome Calendar had crashed.

Version-Release number of selected component:
gnome-calendar-3.28.2-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_stack_set_visible_child_name
executable:     /usr/bin/gnome-calendar
journald_cursor: s=6e5624a5a3ba4e8a842106e7b32ab16a;i=24445;b=f0ed2ee6dd4343d9845c5298d07d3b54;m=487205e6b;t=5719dbfc29ea9;x=e3a18def223e315f
kernel:         4.18.0-0.rc5.git4.1.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gtk_stack_set_visible_child_name at gtkstack.c:1839
 #1 select_row at ../src/gcal-quick-add-popover.c:207
 #2 update_default_calendar_row at ../src/gcal-quick-add-popover.c:490
 #8 g_object_notify_queue_thaw at gobject.c:296
 #9 g_object_setv at gobject.c:2250
 #10 g_object_set_property at gobject.c:2531
 #11 on_source_notify at gbinding.c:327
 #17 g_object_notify_by_spec_internal at gobject.c:1175
 #23 g_settings_real_change_event at gsettings.c:386
 #24 ffi_call_unix64 at ../src/x86/unix64.S:76

Potential duplicate: bug 1515336