Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 448426

Summary: [RHEL4/Evo28] depressed Send/Recieve button - evolution hung
Product: Red Hat Enterprise Linux 4 Reporter: Alan Matsuoka <alanm>
Component: evolution28Assignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Matthew Barnes <mbarnes>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.6CC: tao
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-09 19:01:05 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:
Bug Depends On:    
Bug Blocks: 391511    
Attachments:
Description Flags
evolution28-2.8.0-59.el4-send.recieve.botton.stayed.depressed.evolution.hung.tar.gz
none
sosreport
none
evolution28-2.8.0-59.el4-send.recieve.botton.stayed.depressed.evolution.hung.tar.gz none

Description Alan Matsuoka 2008-05-26 18:52:10 UTC 
Description of problem:
 Hello,

I discovered an email sitting in my outbox which should have been sent earlier
this morning. I selected the "Send/Recieve" button and evolution hung. The
button stayed depressed.

I captured gcores and BT's allround.

Previous to the find that I had an email in my outbox I had a SIGABRT on
exchange. I gcored that and saved it away.

Upon startup of this evolution session I had a password prompt for the Task
component. This is rare.

Please see uploaded archive:
evolution28-2.8.0-59.el4-send.recieve.botton.stayed.depressed.evolution.hung.tgz

Regards,
Nick 

Version-Release number of selected component (if applicable):


How reproducible:

happens when evolution-exchange crashes
Steps to Reproduce:
1.
2.
3.
  
Actual results:

evolution hangs
Expected results:

evolution should probably pop up an error or warning dialogue after timing out.

Additional info:

Comments from SEG:

I'm not surprised that evolution was hanging after evolution-exchange crashed.

evolution was waiting on I/O from a non existent evolution-exchange. This is
really not a bug although it's my belief that evolution should either:

1) popup an error dialogue asking if you want to restart evolution
2) have some way of restarting the exchange connection

an application should not just hang because an error condition exists.
Comment 1 Alan Matsuoka 2008-05-26 18:52:15 UTC 
Created attachment 306698 [details]
evolution28-2.8.0-59.el4-send.recieve.botton.stayed.depressed.evolution.hung.tar.gz
Comment 2 Alan Matsuoka 2008-05-26 18:55:42 UTC 
Created attachment 306702 [details]
sosreport
Comment 3 Matthew Barnes 2008-06-09 17:50:38 UTC 
I believe evolution-exchange-storage has some capacity to restart itself if
spawned through bonobo-activation-server.  I think Nick tends to run the backend
processes directly under GDB, which may be related to why Evolution couldn't
recover.  Even still, I agree the behavior is not ideal.

Also, I can't seem to open the attached tarball.  It appears to be corrupted.
Comment 4 Matthew Barnes 2008-06-09 17:54:58 UTC 
Setting status to NEEDINFO in hopes of a new tarball.
Comment 5 Alan Matsuoka 2008-06-09 18:07:15 UTC 
Created attachment 308735 [details]
evolution28-2.8.0-59.el4-send.recieve.botton.stayed.depressed.evolution.hung.tar.gz
Comment 6 Matthew Barnes 2008-06-09 18:37:01 UTC 
Still corrupt, I'm afraid.  Steve Beal indicated he couldn't open the attachment
in IssueTracker either.
Comment 7 Matthew Barnes 2008-06-09 19:01:05 UTC 
Oops, spoke too soon.  The IT attachment is valid.

This is a duplicate of bug #442644.  We've also seen this backtrace in:

  IT #173389 / Bug #442644  and  IT #174905 / Bug #442631

*** This bug has been marked as a duplicate of 442644 ***