Red Hat Bugzilla – Bug 1466943
[abrt] evolution-data-server: icalproperty_isa(): evolution-calendar-factory-subprocess killed by SIGSEGV
Last modified: 2017-12-12 05:29:25 EST
Version-Release number of selected component:
cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory caldav --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx1540x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/1540/3
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor: Fedora Project
runlevel: N 5
Thread no. 1 (10 frames)
#0 icalproperty_isa at /usr/src/debug/libical-2.0.0/src/libical/icalproperty.c:466
#1 icalcomponent_get_next_property at /usr/src/debug/libical-2.0.0/src/libical/icalcomponent.c:439
#2 icalcomponent_get_dtstart at /usr/src/debug/libical-2.0.0/src/libical/icalcomponent.c:1444
#3 e_cal_recur_generate_instances_sync at e-cal-recur.c:358
#4 e_cal_recur_generate_instances at e-cal-recur.c:1336
#5 func_occur_in_time_range at e-cal-backend-sexp.c:207
#6 e_sexp_term_eval at e-sexp.c:806
#7 e_sexp_eval at e-sexp.c:1691
#8 e_cal_backend_sexp_match_comp at e-cal-backend-sexp.c:1266
#9 caldav_get_object_list at e-cal-backend-caldav.c:5180
Created attachment 1293341 [details]
Created attachment 1293342 [details]
Created attachment 1293343 [details]
Created attachment 1293344 [details]
Created attachment 1293345 [details]
Created attachment 1293346 [details]
Created attachment 1293347 [details]
Created attachment 1293348 [details]
Created attachment 1293349 [details]
Created attachment 1293350 [details]
Created attachment 1293351 [details]
Created attachment 1293352 [details]
Created attachment 1293353 [details]
Thanks for a bug report. I do not see from the above why exactly this crashed, only where it crashed. It happened when some client asked for (probably) events in one of your CalDAV calendars (Google calendars are also served by CalDAV) in time range: 20170529T105300Z and 20170710T105300Z. That's the most I see from the backtrace.
Is it anyhow reproducible for your current data, please?
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.