Version-Release number of selected component: evolution-data-server-3.16.5-1.fc22 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory caldav --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx3056x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/3056/2 crash_function: icaltime_days_in_month executable: /usr/libexec/evolution-calendar-factory-subprocess global_pid: 3124 kernel: 4.1.10-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 icaltime_days_in_month at /usr/src/debug/libical-1.0.1/src/libical/icaltime.c:492 #1 icaltimezone_adjust_change at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:1182 #2 icaltimezone_get_utc_offset at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:895 #3 icaltimezone_convert_time at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:807 #4 icaltime_convert_to_zone at /usr/src/debug/libical-1.0.1/src/libical/icaltime.c:978 #5 generate_instances_for_chunk at e-cal-recur.c:1294 #6 e_cal_recur_generate_instances_of_rule at e-cal-recur.c:868 #7 e_cal_recur_generate_instances at e-cal-recur.c:640 #8 func_occur_in_time_range at e-cal-backend-sexp.c:207 #9 e_sexp_term_eval at e-sexp.c:781 Potential duplicate: bug 1176376
Created attachment 1088204 [details] File: backtrace
Created attachment 1088205 [details] File: cgroup
Created attachment 1088206 [details] File: core_backtrace
Created attachment 1088207 [details] File: dso_list
Created attachment 1088208 [details] File: environ
Created attachment 1088209 [details] File: limits
Created attachment 1088210 [details] File: maps
Created attachment 1088211 [details] File: mountinfo
Created attachment 1088212 [details] File: namespaces
Created attachment 1088213 [details] File: open_fds
Created attachment 1088214 [details] File: proc_pid_status
Created attachment 1088215 [details] File: var_log_messages
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate. *** This bug has been marked as a duplicate of bug 1176376 ***