Description of problem: reboot system Version-Release number of selected component: evolution-3.4.4-2.fc17 Additional info: libreport version: 2.0.16 abrt_version: 2.0.16 backtrace_rating: 4 cmdline: evolution crash_function: talloc_abort kernel: 3.6.2-4.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #2 talloc_abort at ../talloc.c:317 : #3 talloc_abort_access_after_free at ../talloc.c:336 : #4 talloc_chunk_from_ptr at ../talloc.c:357 : #6 __talloc at ../talloc.c:555 : #7 _talloc_named_const at ../talloc.c:669 : #8 _talloc_array at ../talloc.c:2217 : #9 smb_iconv at ../lib/util/charset/iconv.c:139 : #10 convert_string_talloc_handle at ../lib/util/charset/convert_string.c:421 : #11 convert_string_talloc at ../lib/util/charset/convert_string.c:541 : #12 ndr_pull_string at ../librpc/ndr/ndr_string.c:157
Created attachment 636097 [details] File: core_backtrace
Created attachment 636098 [details] File: environ
Created attachment 636099 [details] File: limits
Created attachment 636100 [details] File: backtrace
Created attachment 636101 [details] File: cgroup
Created attachment 636102 [details] File: smolt_data
Created attachment 636103 [details] File: maps
Created attachment 636105 [details] File: dso_list
Created attachment 636106 [details] File: build_ids
Created attachment 636107 [details] File: proc_pid_status
Created attachment 636108 [details] File: var_log_messages
Created attachment 636109 [details] File: open_fds
Thanks for a bug report. I see the talloc detected use-after-free of a memory chunk under ndr_pull_string(), though the backtrace doesn't show why that happened, which is common in this kind of bugs. If I got it right, then you just started evolution after restart, and based on the backtrace, it was in the middle of a folder update, when the crash happened. I guess you cannot reproduce this reliably, can you? (It might be when there was received a new message in the folder or something like that - I only see in the backtrace that this happened when evolution-mapi was listing messages in the folder). There is one thing in the backtrace I do not understand, your evolution 3.4.4 is showing a thread, which involves code from webkit, but evolution uses webkit only since 3.6.0, thus I'm wondering how this could happen. Do you compile your own evolution, or is it used by other 3rd party plugins, like evolution-rss?
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.