Bug 505166

Summary: Evo crashes while refreshing inbox via MAPI
Product: [Fedora] Fedora Reporter: Matthew Saltzman <mjs>
Component: evolution-mapiAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: mbarnes
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: 2009-06-13 11:00:49 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
Console messages from crash instance none

Description Matthew Saltzman 2009-06-10 20:53:37 UTC 
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.
Comment 1 Matthew Saltzman 2009-06-10 20:54:26 UTC 
Created attachment 347291 [details]
Console messages from crash instance
Comment 2 Matthew Barnes 2009-06-13 11:00:49 UTC 
Moving this upstream for better visibility.  Please see [1] for further updates.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=585637
Comment 3 Matthew Saltzman 2009-06-24 16:01:15 UTC 
A patch has been committed here: http://bugzilla.gnome.org/show_bug.cgi?id=584072.  I hope this can be pulled into the Fedora package soon.