Red Hat Bugzilla – Bug 448426
[RHEL4/Evo28] depressed Send/Recieve button - evolution hung
Last modified: 2008-06-09 15:01:11 EDT
Description of problem:
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:
Version-Release number of selected component (if applicable):
happens when evolution-exchange crashes
Steps to Reproduce:
evolution should probably pop up an error or warning dialogue after timing out.
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.
Created attachment 306698 [details]
Created attachment 306702 [details]
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.
Setting status to NEEDINFO in hopes of a new tarball.
Created attachment 308735 [details]
Still corrupt, I'm afraid. Steve Beal indicated he couldn't open the attachment
in IssueTracker either.
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 ***