Version-Release number of selected component: evolution-data-server-3.24.2-2.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2165x6 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2165/6 crash_function: icaltimezone_compare_change_fn executable: /usr/libexec/evolution-calendar-factory-subprocess journald_cursor: s=375888cef57b49058eeb2f3c24389c57;i=ce495;b=94bf791f0c1c409c9c7566c8b7471e60;m=21181ffd18;t=551fe463ea415;x=8719047cc4a4500e kernel: 4.11.4-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 icaltimezone_compare_change_fn at /usr/src/debug/libical-2.0.0/src/libical/icaltimezone.c:701 #1 icaltimezone_find_nearby_change at /usr/src/debug/libical-2.0.0/src/libical/icaltimezone.c:1021 #2 icaltimezone_get_utc_offset at /usr/src/debug/libical-2.0.0/src/libical/icaltimezone.c:798 #3 icaltimezone_convert_time at /usr/src/debug/libical-2.0.0/src/libical/icaltimezone.c:743 #4 icaltime_convert_to_zone at /usr/src/debug/libical-2.0.0/src/libical/icaltime.c:1027 #5 icaltime_compare at /usr/src/debug/libical-2.0.0/src/libical/icaltime.c:782 #6 e_cal_recur_generate_instances_sync at /usr/src/debug/evolution-data-server-3.24.2/src/calendar/libecal/e-cal-recur.c:447 #7 e_cal_recur_generate_instances at /usr/src/debug/evolution-data-server-3.24.2/src/calendar/libecal/e-cal-recur.c:1334 #8 func_occur_in_time_range at /usr/src/debug/evolution-data-server-3.24.2/src/calendar/libedata-cal/e-cal-backend-sexp.c:205 #9 e_sexp_term_eval at /usr/src/debug/evolution-data-server-3.24.2/src/libedataserver/e-sexp.c:804 Potential duplicate: bug 772572
Created attachment 1288317 [details] File: backtrace
Created attachment 1288318 [details] File: cgroup
Created attachment 1288319 [details] File: core_backtrace
Created attachment 1288320 [details] File: cpuinfo
Created attachment 1288321 [details] File: dso_list
Created attachment 1288322 [details] File: environ
Created attachment 1288323 [details] File: limits
Created attachment 1288324 [details] File: maps
Created attachment 1288325 [details] File: open_fds
Created attachment 1288326 [details] File: proc_pid_status
Created attachment 1288327 [details] File: var_log_messages
Created attachment 1288328 [details] File: exploitable
Thanks for a bug report. If I read the backtrace properly then it crashed when one of your EWS calendars had been searching for events between June 8th and July 20th 2017, and one weekly event witch starts on 2016-02-26, between 12:00 and 13:00, caused the crash when checking its timezone information, though I do not see what timezone is that event entered for. Another thread is searching for "Russia Time Zone 3", which comes from the server, I believe. This reminded me of [1], but as you have 3.24.2, then it is not the case, or the change there doesn't cover everything. By any chance, are you able to reproduce it consistently? It can be even only when the calendar changed, which you can mimic by deleting the local cache in ~/.cache/evolution/calendar/ and then re-starting /usr/libexec/evolution-calendar-factory -w after which (give it like 5 seconds, to have D-Bus register it) run evolution. [1] https://bugzilla.gnome.org/show_bug.cgi?id=634294
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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' of '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.