Red Hat Bugzilla – Bug 1009395
[abrt] evolution-data-server-3.8.5-4.fc19: __memset_sse2: Process /usr/libexec/evolution-calendar-factory was killed by signal 11 (SIGSEGV)
Last modified: 2014-06-12 03:01:27 EDT
Description of problem:
Imported an ics attachment received by mail.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 __memset_sse2 at ../sysdeps/x86_64/memset.S:334
#1 memset at /usr/include/bits/string3.h:84
#2 e_memchunk_alloc0 at e-memory.c:151
#3 e_sexp_result_new at e-sexp.c:191
#4 e_sexp_term_eval at e-sexp.c:751
#7 e_sexp_eval at e-sexp.c:1698
#8 e_cal_backend_sexp_match_comp at e-cal-backend-sexp.c:1254
#9 e_data_cal_view_component_matches at e-data-cal-view.c:966
#10 e_cal_backend_notify_component_created at e-cal-backend.c:1750
#11 put_server_comp_to_cache at e-cal-backend-caldav.c:3159
Created attachment 799317 [details]
Created attachment 799318 [details]
Created attachment 799319 [details]
Created attachment 799320 [details]
Created attachment 799321 [details]
Created attachment 799322 [details]
Created attachment 799323 [details]
Created attachment 799324 [details]
Created attachment 799325 [details]
Created attachment 799326 [details]
Thanks for a bug report. I see that the Google backend was asked for a component, which it did not find, thus it asked the Google server and it found it, and while the CalDAV backend tried to put the just downloaded component into its local cache a crash happened. Are you able to reproduce the crash with the ics attachment email consistently? If I understand the consequences correctly, then you just selected the message in evolution, which recognized an iCalendar attachment, and it tried to find it in your calendars.
I am sorry, I am using a newer version nowadays and don't recall which email caused the crash.
Thanks for an update. I realized there had been filled another similar bug report meanwhile, which was moved upstream, thus let's move there too.
*** This bug has been marked as a duplicate of bug 1013213 ***