Bug 969113

Summary: [abrt] evolution-3.8.2-1.fc19: camel_mime_filter_crlf_new: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kjartan Maraas <kmaraas>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: kmaraas, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1024ba1d0237b32176edce1b136d77a451e59561
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-03 15:02:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Kjartan Maraas 2013-05-30 16:49:40 UTC 
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
Comment 1 Kjartan Maraas 2013-05-30 16:49:45 UTC 
Created attachment 754967 [details]
File: backtrace
Comment 2 Kjartan Maraas 2013-05-30 16:49:48 UTC 
Created attachment 754968 [details]
File: cgroup
Comment 3 Kjartan Maraas 2013-05-30 16:49:51 UTC 
Created attachment 754969 [details]
File: core_backtrace
Comment 4 Kjartan Maraas 2013-05-30 16:49:55 UTC 
Created attachment 754970 [details]
File: dso_list
Comment 5 Kjartan Maraas 2013-05-30 16:49:58 UTC 
Created attachment 754971 [details]
File: environ
Comment 6 Kjartan Maraas 2013-05-30 16:50:01 UTC 
Created attachment 754972 [details]
File: limits
Comment 7 Kjartan Maraas 2013-05-30 16:50:05 UTC 
Created attachment 754973 [details]
File: maps
Comment 8 Kjartan Maraas 2013-05-30 16:50:09 UTC 
Created attachment 754974 [details]
File: open_fds
Comment 9 Kjartan Maraas 2013-05-30 16:50:13 UTC 
Created attachment 754975 [details]
File: proc_pid_status
Comment 10 Kjartan Maraas 2013-05-30 16:50:16 UTC 
Created attachment 754976 [details]
File: var_log_messages
Comment 11 Milan Crha 2013-06-03 10:38:53 UTC 
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?
Comment 12 Kjartan Maraas 2013-06-03 12:41:10 UTC 
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 :-)
Comment 13 Milan Crha 2013-06-03 15:02:00 UTC 
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).