Red Hat Bugzilla – Bug 969113
[abrt] evolution-3.8.2-1.fc19: camel_mime_filter_crlf_new: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2013-06-03 11:02:00 EDT
Description of problem: Version-Release number of selected component: evolution-3.8.2-1.fc19 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: evolution crash_function: camel_mime_filter_crlf_new executable: /usr/bin/evolution kernel: 3.9.4-300.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 camel_mime_filter_crlf_new at /lib64/libcamel-1.2.so.43 #1 data_wrapper_decode_to_stream_sync at /lib64/libcamel-1.2.so.43 #2 camel_data_wrapper_decode_to_stream_sync at /lib64/libcamel-1.2.so.43 #3 e_mail_formatter_format_text at /usr/lib64/evolution/3.8/libemformat.so #4 emfe_text_html_format at /usr/lib64/evolution/3.8/libemformat.so #5 e_mail_formatter_format_as at /usr/lib64/evolution/3.8/libemformat.so #6 handle_mail_request at /usr/lib64/evolution/3.8/libevolution-mail.so #7 run_in_thread at /lib64/libgio-2.0.so.0 #8 io_job_thread at /lib64/libgio-2.0.so.0 #9 g_task_thread_pool_thread at /lib64/libgio-2.0.so.0
Created attachment 754967 [details] File: backtrace
Created attachment 754968 [details] File: cgroup
Created attachment 754969 [details] File: core_backtrace
Created attachment 754970 [details] File: dso_list
Created attachment 754971 [details] File: environ
Created attachment 754972 [details] File: limits
Created attachment 754973 [details] File: maps
Created attachment 754974 [details] File: open_fds
Created attachment 754975 [details] File: proc_pid_status
Created attachment 754976 [details] File: var_log_messages
Thanks for a bug report. I see the backtrace has only some basic debug information, it's missing all details. From the basic information I see that this happened when you chose certain message to view, but that's the most I see from it. Are you able to reproduce this crash with any message intentionally, please?
Haven't seen it since and I'm not sure I can trigger it again. I'll install more debuginfo packages in case it happens again. You can close this until that happens :-)
OK, thanks. Try to see when it happens, with which message and whether reproducible with it. I would also check evolution's console, to see whether anything shows there (it sometimes can only claim on console, instead of crashing).