After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 584643 - evolution mail application crashes when kept open and when using other mail client
evolution mail application crashes when kept open and when using other mail c...
Status: RESOLVED DUPLICATE of bug 550414
Product: evolution
Classification: Applications
Component: Do Not Use
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Executive Summary maintaintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-06-02 18:56 UTC by Sirish
Modified: 2013-09-13 12:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
Bug report to Bug number 584643 about evolution crashing (388.53 KB, text/plain)
2009-06-02 18:58 UTC, Sirish
Details

Description Sirish 2009-06-02 18:56:58 UTC
Steps to reproduce:
1. Open evolution, to read/send email.
2. from a terminal, open another mail client (in my case it was mutt)
3. now, when you get back to evolution and press send/receive, the application is stuck.... closing through forced quit also did not happen. Only kill -9 (psid of evolution) works.


Stack trace:
I tried pasting the bug-report, but it says we cannot have more than 65K characters. Please mail me to get the bug report.

Other information:
Comment 1 Sirish 2009-06-02 18:58:24 UTC
Created attachment 135836 [details]
Bug report to Bug number 584643 about evolution crashing
Comment 2 Akhil Laddha 2009-06-03 05:02:11 UTC
x-session error says Summary and folder mismatch, even after a sync, you may hit by bug 550414 

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 3 Sirish 2009-06-04 15:49:55 UTC
I have attached a bug report. I am not able to reproduce the scenario again, but it happens randomly over several weeks. Let me get a trace the next time it happens. Till then, wouldnt this bug report I attached work?
Comment 4 Akhil Laddha 2009-07-17 04:48:06 UTC
Traces attached in comment#1 aren't useful. In case you aren't able to provide more update, i will mark the bug as duplicate. 
Comment 5 Akhil Laddha 2009-08-27 07:37:26 UTC

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