Version-Release number of selected component: evolution-data-server-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: icalarray_element_at executable: /usr/libexec/evolution-calendar-factory kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 icalarray_element_at at /usr/src/debug/libical-1.0/src/libical/icalarray.c:147 #1 icaltimezone_get_utc_offset at /usr/src/debug/libical-1.0/src/libical/icaltimezone.c:920 #2 icaltimezone_convert_time at /usr/src/debug/libical-1.0/src/libical/icaltimezone.c:797 #3 icaltime_as_timet_with_zone at /usr/src/debug/libical-1.0/src/libical/icaltime.c:415 #4 e_cal_recur_generate_instances_of_rule at e-cal-recur.c:765 #5 e_cal_recur_generate_instances at e-cal-recur.c:640 #6 func_occur_in_time_range at e-cal-backend-sexp.c:200 #7 e_sexp_term_eval at e-sexp.c:784 #8 term_eval_and at e-sexp.c:288 #9 e_sexp_term_eval at e-sexp.c:772
Created attachment 845464 [details] File: backtrace
Created attachment 845465 [details] File: cgroup
Created attachment 845466 [details] File: core_backtrace
Created attachment 845467 [details] File: dso_list
Created attachment 845468 [details] File: environ
Created attachment 845469 [details] File: exploitable
Created attachment 845470 [details] File: limits
Created attachment 845471 [details] File: maps
Created attachment 845472 [details] File: open_fds
Created attachment 845473 [details] File: proc_pid_status
Created attachment 845474 [details] File: var_log_messages
I don't know what leads to this crash. But the evolution worked till before normally and suddenly the calendar backend keeps crashing.
Somehow (I don't know yet) I got a lot of duplicates of my birthday reminders in my calendar (synchronized with Owncloud). Each of them around five times duplicated. After deleting those it looks like evolution is working normally again.
*** Bug 1048519 has been marked as a duplicate of this bug. ***
Thanks for a bug report. The related code is used when a client asks for a list of events in a certain time range. There are filled similar bug reports upstream, which suggests that the issue might be with libical itself and its array of timezones. The thing is that this happens only in certain cases, most likely only when the used events have used certain time zones (the set of timezones, certain count of them). I was not able to reproduce this myself on will, but I see from the ABRT reports that you managed to reproduce this twice, and you even mention that more than twice, which makes me wonder what calendar content may make this reproducible. You mentioned ownCloud, does it mean that you deleted 4 of 5 birthday reminders there and then it begun to work? I believe the calendar view content is the way to reproduce this, though it feels unlikely that the events in ownCloud has set different timezones.
For some reason the issue starts occurring again today :-( even with not duplicated birthdays. I don't use different time zones at least not on will.
Sorry. When skipping through the calendar, duplicated birthday have been created again for some reason.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.