Hide Forgot
abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: evolution component: evolution crash_function: raise executable: /usr/bin/evolution kernel: 2.6.34.6-47.fc13.i686 package: evolution-2.30.3-1.fc13 rating: 4 reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1283957121 uid: 500 comment ----- Found the following lines in the file ~/.evolution/mail/config/state and removed the the whole SearchText line. After that Evolution starts normally. [Folder mapi://user@server/Mailbox%20-%20lastname%20firstname/Inbox] Expanded=true GroupByThreads=true SearchFilter=mail-filter-all-messages SearchOption=mail-search-body-contains SearchText=search words How to reproduce ----- 1. Entered search in the body of messages in the Inbox for two words with space between. After that Evolution crashes right away when starting. Same thing happens if there is only one word in the search.
Created an attachment (id=446006) File: backtrace
Package: evolution-2.30.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. told evolution to sync mail to local disk 2. went away - screen saver kicks in 3. come back to crash report Comment ----- more crashes from evoultion with mapi connector.
Package: evolution-2.30.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. setup mapi connection for evolution 2. point at exchange server 3. let mail sync 4. click file > download messages for offline use 5. watch evolution crash Comment ----- yet another way to make evoultion crash when using the mapi connector. this is a crash on demand. I can repoduce on my v-box guest every time without fail. have not been able to test on a non virutal machine yet. if anyone needs more information about this please be very explict about you need run as I am not experinced with debugging apps or anything along those lines.
Package: evolution-2.30.3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.It just happened when I opened evolution. 2. 3.
Package: evolution-2.30.3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start Evolution (2 accounts (gmail, corporate exchange server) 2. Enter password for exchange server 3. while loading the email messages it crashes. Comment ----- I will try to delete the .evolution folder en redo all the settings and see if this solves the problem.
*** Bug 579822 has been marked as a duplicate of this bug. ***
*** Bug 597587 has been marked as a duplicate of this bug. ***
*** Bug 599118 has been marked as a duplicate of this bug. ***
*** Bug 599186 has been marked as a duplicate of this bug. ***
*** Bug 599557 has been marked as a duplicate of this bug. ***
*** Bug 600458 has been marked as a duplicate of this bug. ***
*** Bug 600899 has been marked as a duplicate of this bug. ***
*** Bug 606690 has been marked as a duplicate of this bug. ***
*** Bug 606692 has been marked as a duplicate of this bug. ***
*** Bug 607852 has been marked as a duplicate of this bug. ***
*** Bug 609315 has been marked as a duplicate of this bug. ***
*** Bug 609316 has been marked as a duplicate of this bug. ***
*** Bug 617206 has been marked as a duplicate of this bug. ***
*** Bug 623793 has been marked as a duplicate of this bug. ***
*** Bug 625415 has been marked as a duplicate of this bug. ***
*** Bug 638280 has been marked as a duplicate of this bug. ***
*** Bug 642871 has been marked as a duplicate of this bug. ***
*** Bug 648426 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.