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 585637 - Evo crashes while refreshing inbox via MAPI
Evo crashes while refreshing inbox via MAPI
Status: RESOLVED DUPLICATE of bug 579819
Product: evolution-mapi
Classification: Applications
Component: Mail
0.27.x
Other Linux
: Normal critical
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2009-06-13 10:59 UTC by Matthew Barnes
Modified: 2009-06-15 04:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthew Barnes 2009-06-13 10:59:46 UTC 
Forwarding this from a Fedora bug:
http://bugzilla.redhat.com/show_bug.cgi?id=505166

Description of problem:
My Exchange MAPI inbox shows the correct number of messages, but no message
headers appear.  When I try to refresh, evo crashes after about 20% of messages
are downloaded.

Version-Release number of selected component (if applicable):
evolution-mapi-0.26.1-1.fc11.x86_64
openchange-0.8.2-2.fc11.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open evo
2. Right-click INBOX in MAPI account
3. Select refresh

Actual results:
Crash

Expected results:
No crash--list of messages

Additional info:

Running from the command line, I get messages in the attached file.  It seems
as though there is a message with some sort of problem header, but I have no
idea how to find it and delete it with the information provided in the crash. 
This is not a very robust failure mode.  

Attachment:
Console messages from crash instance
https://bugzilla.redhat.com/attachment.cgi?id=347291
Comment 1 Akhil Laddha 2009-06-15 04:59:44 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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