Version-Release number of selected component: evolution-3.6.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: _int_malloc executable: /usr/bin/evolution kernel: 3.6.7-5.fc18.x86_64 remote_result: 842259 uid: 500 var_log_messages: Nov 27 13:37:27 liliana abrt[12185]: Saved core dump of pid 19816 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2012-11-27-13:37:14-19816 (1736257536 bytes) xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #1 malloc at /lib64/libc.so.6 #2 g_realloc at /lib64/libglib-2.0.so.0 #3 g_array_maybe_expand at /lib64/libglib-2.0.so.0 #4 g_array_append_vals at /lib64/libglib-2.0.so.0 #5 g_byte_array_append at /lib64/libglib-2.0.so.0 #6 stream_mem_write at /lib64/libcamel-1.2.so.40 #7 camel_stream_write at /lib64/libcamel-1.2.so.40 #8 camel_stream_write_to_stream at /lib64/libcamel-1.2.so.40 #9 data_wrapper_construct_from_stream_sync at /lib64/libcamel-1.2.so.40 #10 camel_data_wrapper_construct_from_stream_sync at /lib64/libcamel-1.2.so.40
Created attachment 652678 [details] File: backtrace
Created attachment 652680 [details] File: build_ids
Created attachment 652682 [details] File: cgroup
Created attachment 652685 [details] File: core_backtrace
Created attachment 652686 [details] File: dso_list
Created attachment 652687 [details] File: environ
Created attachment 652688 [details] File: limits
Created attachment 652689 [details] File: maps
Created attachment 652690 [details] File: open_fds
Created attachment 652691 [details] File: proc_pid_status
Created attachment 652692 [details] File: smolt_data
Thanks for a bug rpeort. I see from the backtrace that this broke when you selected a message with inline PGP signature. I have some similar messages, but they are shown properly, thus I would like to ask you, if you've it reproducible with certain message, could you add it here, or send it to my bugzilla email (at attachment, the best is compressed by a zip or something), thus I'll be able to test it here, please? Thanks in advance.
Yep, but that's a private mail so I would prefer to not have it published. I will send it privately.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.