Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 71162 bytes cmdline: evolution component: evolution Attached file: coredump, 168554496 bytes crash_function: malloc_consolidate executable: /usr/bin/evolution kernel: 2.6.35.13-91.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: 1307436398 uid: 16777216 How to reproduce ----- 1. Search message list. 2. 3.
Created attachment 503412 [details] File: backtrace
Thanks for a bug report. I see this crashed in a libmapi, on a talloc free. I saw similar bug report upstream [1], but it was not reproducible on demand, thus the mentioned fix in there wasn't confirmed. Are you able to reproduce this after some certain steps, or it is just an occasional crash? [1] https://bugzilla.gnome.org/show_bug.cgi?id=627058
(In reply to comment #2) > Are you able to reproduce > this after some certain steps, or it is just an occasional crash? Now I have another problem with Evolution, MAPI and Exchange 2010 which prevent me from using Evolution at all - so cannot promise. X:-(
(In reply to comment #3) > Now I have another problem with Evolution, MAPI and Exchange 2010 which prevent > me from using Evolution at all - so cannot promise. X:-( What is it?
(In reply to comment #4) > What is it? My mailbox was moved to Exchange 2010 server. First I was not able to see new messages - so I have to switch to new server manually. But after it I'm getting authentication failure. Have not posted bug as I need to check Exchange config first.
The easiest way is to disable the previous account, stop evolution, start evolution, edit the existing account, together with changing the address and/or credentials, authenticate the account and only after the successful authentication enable the account again. Or just remove the old account and create a new fresh. (The stop & start evolution steps are good to free any possible internal evolution caches with the old account data.)
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