After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789129 - Calendar crashes with segmentation fault when opened
Calendar crashes with segmentation fault when opened
Status: RESOLVED OBSOLETE
Product: gnome-calendar
Classification: Applications
Component: Backend
3.26.x
Other Linux
: Normal normal
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
Depends on:
Blocks:
 
 
Reported: 2017-10-18 05:55 UTC by gbug
Modified: 2017-11-24 22:41 UTC
See Also:
GNOME target: ---
GNOME version: 3.25/3.26



Description gbug 2017-10-18 05:55:11 UTC
After updating to the version 3.26.2 of gnome-calendar, the app crashes on startup. On the opened window, I can see that gnome-calendar starts to load the calendar via DAV. Then the window closes.

gnome-calendar: Version 3.26.2

Log output:

segmentation fault (core dumped)  gnome-calendar

Process 9791 (gnome-calendar) of user 1000 dumped core.

Stack trace of thread 9791:
#0  0x0000557fdc584829 icaltime_to_datetime (gnome-calendar)
#1  0x0000557fdc56e446 gcal_event_widget_sort_events (gnome-calendar)
#2  0x00007fb004a890d3 n/a (libglib-2.0.so.0)
#3  0x0000557fdc57b324 n/a (gnome-calendar)
#4  0x00007fb004d59e0a g_cclosure_marshal_VOID__OBJECTv (libgobject-2.0.so.0)
#5  0x00007fb004d73c01 g_signal_emit_valist (libgobject-2.0.so.0)
#6  0x00007fb004d74920 g_signal_emit (libgobject-2.0.so.0)
#7  0x00007fb006204546 gtk_container_add (libgtk-3.so.0)
#8  0x0000557fdc57e675 n/a (gnome-calendar)
#9  0x0000557fdc57f0f9 n/a (gnome-calendar)
#10 0x0000557fdc57fb80 n/a (gnome-calendar)
#11 0x0000557fdc580672 n/a (gnome-calendar)
#12 0x00007fb004d59ec2 g_cclosure_marshal_VOID__POINTERv (libgobject-2.0.so.0)
#13 0x00007fb004d73c01 g_signal_emit_valist (libgobject-2.0.so.0)
#14 0x00007fb004d74920 g_signal_emit (libgobject-2.0.so.0)
#15 0x00007fb0047ed86e n/a (libecal-1.2.so.19)
#16 0x00007fb004a8b0be g_main_context_dispatch (libglib-2.0.so.0)
#17 0x00007fb004a8cf69 n/a (libglib-2.0.so.0)
#18 0x00007fb004a8cfae g_main_context_iteration (libglib-2.0.so.0)
#19 0x00007fb004fdc1ce g_application_run (libgio-2.0.so.0)
#20 0x0000557fdc555cd9 main (gnome-calendar)
#21 0x00007fb006ea7f6a __libc_start_main (libc.so.6)
#22 0x0000557fdc555d2a _start (gnome-calendar)
Comment 1 Georges Basile Stavracas Neto 2017-11-24 22:41:20 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/198.