Bug 587290

Summary: [abrt] crash in evolution-2.28.3-1.fc12: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Al Schapira <a.schapira>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dwayne, lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:3a3affcdf1cc169fdb4eac67a97f0ab9eecd8786
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 15:18:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Al Schapira 2010-04-29 14:36:16 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution --component=mail
component: evolution
executable: /usr/bin/evolution
global_uuid: 3a3affcdf1cc169fdb4eac67a97f0ab9eecd8786
kernel: 2.6.32.11-99.fc12.i686
package: evolution-2.28.3-1.fc12
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Al Schapira 2010-04-29 14:36:19 UTC
Created attachment 410126 [details]
File: backtrace

Comment 2 Dwayne Bailey 2010-05-19 06:10:47 UTC
Package: evolution-2.28.3-1.fc12
Architecture: i686
OS Release: Fedora release 12 (Constantine)


Comment
-----
Ctrl-E after doing some spam filtering

Comment 3 Dwayne Bailey 2010-05-20 05:26:04 UTC
Package: evolution-2.28.3-1.fc12
Architecture: i686
OS Release: Fedora release 12 (Constantine)


Comment
-----
Was downloading new mail.  Clicked on Inox, then onto junk then tried inbox again when it then crashed.

Comment 4 Dwayne Bailey 2010-05-20 08:39:13 UTC
Package: evolution-2.28.3-1.fc12
Architecture: i686
OS Release: Fedora release 12 (Constantine)


Comment
-----
Unsure of what was happening at the time.

Comment 5 Karel Klíč 2010-05-25 08:44:34 UTC
*** Bug 593942 has been marked as a duplicate of this bug. ***

Comment 6 Bug Zapper 2010-11-03 16:02:50 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 7 Bug Zapper 2010-12-03 15:18:04 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.