Description of problem: Started the PC, logged in and didn't even get to do anything when evolution (i hadn't started it) crashed. Version-Release number of selected component: evolution-data-server-3.6.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: icaltimezone_get_utc_offset executable: /usr/libexec/evolution-calendar-factory kernel: 3.6.10-4.fc18.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Dec 19 16:37:31 arrakis abrt[1931]: Saved core dump of pid 1894 (/usr/libexec/evolution-calendar-factory) to /var/spool/abrt/ccpp-2012-12-19-16:37:30-1894 (113704960 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 icaltimezone_get_utc_offset at icaltimezone.c:905 #1 icaltimezone_convert_time at icaltimezone.c:773 #2 icaltime_as_timet_with_zone at icaltime.c:415 #3 componenttime_to_utc_timet at e-cal-util.c:1213 #4 e_cal_util_get_component_occur_times at e-cal-util.c:1255 #5 scan_vcalendar at e-cal-backend-file-store.c:668 #6 e_cal_backend_file_store_load at e-cal-backend-file-store.c:702 #7 e_cal_backend_store_load at e-cal-backend-store.c:165 #8 initialize_backend at e-cal-backend-caldav.c:2700 #9 caldav_do_open at e-cal-backend-caldav.c:2787 Potential duplicate: bug 708199
Created attachment 666139 [details] File: backtrace
Created attachment 666140 [details] File: cgroup
Created attachment 666141 [details] File: core_backtrace
Created attachment 666142 [details] File: dso_list
Created attachment 666143 [details] File: environ
Created attachment 666144 [details] File: limits
Created attachment 666145 [details] File: maps
Created attachment 666146 [details] File: open_fds
Created attachment 666147 [details] File: proc_pid_status
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate. Here crashed evolution-calendar-factory process, which allows clients to access calendar items, like for the evolution-alarm-notify or gnome-shell's Calendar applet/extension. *** This bug has been marked as a duplicate of bug 880864 ***