Bug 682490

Summary: [abrt] evolution-2.30.3-1.fc13: mail_store_add: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Timothy Ward <timwa1>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:2ffe75bb1cdbb065399e4fb8de47ffc1a3b67c9f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 12:03:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Timothy Ward 2011-03-06 01:58:32 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: evolution
comment: The bug does not happen every time but does occur at a regular interval to be annoying. Usually no other applications open when this occurs, has corrupted the folders.db filter on previous occasions, this is the first time that Arbt has processed the crash report. Has not happened during a Evolution back-up to date but does happen usually when moving messages out of the Inbox to another folder by drag and drop method.
component: evolution
crash_function: mail_store_add
executable: /usr/bin/evolution
kernel: 2.6.34.7-66.fc13.i686.PAE
package: evolution-2.30.3-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1299375118
uid: 500

How to reproduce
-----
1. Opened evolution and deleted several meesages from Inbox, then
2. After moving several messages to different folders , Attempted to move a messages from Inbox to another Folder and
3. Evolution Crashed
Comment 1 Timothy Ward 2011-03-06 01:58:37 UTC 
Created attachment 482483 [details]
File: backtrace
Comment 2 Bug Zapper 2011-05-30 11:05:52 UTC 
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
Comment 3 Bug Zapper 2011-06-27 12:03:52 UTC 
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.