Bug 588180

Summary: Evolution client hangs while retrieving email
Product: [Fedora] Fedora Reporter: Penelope Fudd <bugzilla.redhat.com>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 12CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 15:10:16 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
Output of 'pstack `pidof evolution`' for frozen evolution none

Description Penelope Fudd 2010-05-03 01:59:48 UTC
Created attachment 410886 [details]
Output of 'pstack `pidof evolution`' for frozen evolution

Description of problem:
Frequently the user interface to Evolution hangs randomly.  May be related to fetching mail and gnome keyring passwords.

Version-Release number of selected component (if applicable):
evolution-2.28.3-1.fc12.i686

How reproducible:
Unknown, but happens many times a day.

Steps to Reproduce:
1. Open Evolution
2. Use it to read email, or write email
3. Go away for a while

Actual results:
Come back to find Evolution window not updating, dragging other windows across it will erase the contents of the evolution window.

Expected results:
No hanging

Additional info:
I captured the output of 'pstack `pidof evolution`' on the last hang, see attached.

Comment 1 Milan Crha 2010-05-03 10:24:45 UTC
Thanks for a bug report. The trace shows it has really something to do with gnome-keyring, but there are missing some debug information to see the whole context. Could you install debug info packages for evolution-data-server, evolution and gnome-keyring,and update the backtrace, please? Thanks in advance.

Please note that there is not planned any update for 2.28, thus maybe if you can switch to Fedora 13 with 2.30 version, then it'll be also better.

Comment 2 Penelope Fudd 2010-05-03 14:09:49 UTC
Ok, I'll try Fedora 13 in 2 weeks.

Comment 3 Bug Zapper 2010-11-03 15:47:53 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 4 Bug Zapper 2010-12-03 15:10:16 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.