Hide Forgot
abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 125845 bytes cmdline: evolution component: evolution Attached file: coredump, 180072448 bytes crash_function: _int_malloc executable: /usr/bin/evolution kernel: 2.6.35.11-83.fc14.x86_64 package: evolution-2.32.2-1.fc14 rating: 4 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1300813792 uid: 500 How to reproduce ----- 1. Crashed while refreshing folders.
Created attachment 486850 [details] File: backtrace
Thanks for a bug report. This seems to be like some memory corruption crash, or something like that, because this crashed when trying to allocate some memory, but other thread are idle. The ABRT unfortunately doesn't send console messages, so whether it claimed anything or not is hidden to me. Did you get similar crash more than once, please? If so, could you run evolution from console and attach also console messages from it, please? Or change your evolution starter to something like: evolution &>/tmp/log.txt and when it crashes, then attach also that /tmp/log.txt file, to see whether there will be anything useful, a hint why the application crashed. Thanks in advance.
Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. App was idle in background. 2. 3.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping