Bug 520805

Summary: evolution-exchange crashes in sync_deletions()
Product: Red Hat Enterprise Linux 5 Reporter: Olivier Fourdan <ofourdan>
Component: evolution-connectorAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 5.4CC: dmair, james.brown, kem, sbeal
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-07 01:32:54 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: 743405, 1002709    
Attachments:
Description Flags
Proposed patch (from upstream fix for bug #522277)
none
Bactrace from Bug buddy none

Description Olivier Fourdan 2009-09-02 13:32:03 UTC 
Created attachment 359519 [details]
Proposed patch (from upstream fix for bug #522277)

Description of problem:

Customer reported a crash of evolution-exchange. Backtrace shows the crash occured in sync_deletions() from evolution-exchange/mail/mail-stub-exchange.c

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

evolution-connector-2.12.3-11

How reproducible:

Unknown

Steps to Reproduce:

Unknown - This happened while using Evo with Exchange but there is no detailed reproducing steps.
  
Actual results:

evolution-connector crashed

Expected results:

evolution-connector does not crash

Additional info:

Based on the backtrace from bug-buddy I think this is upstream bug #522277 -  ("crash in Evolution: sending, receiving, dele..."):

  http://bugzilla.gnome.org/show_bug.cgi?id=522277
Comment 1 Olivier Fourdan 2009-09-02 13:36:26 UTC 
Created attachment 359521 [details]
Bactrace from Bug buddy

Attaching the backtrace reported by bug-buddy at the time of the crash.
Comment 4 RHEL Program Management 2009-11-06 19:19:16 UTC 
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Comment 7 RHEL Program Management 2010-08-09 19:38:02 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 8 RHEL Program Management 2011-05-31 15:10:37 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 10 RHEL Program Management 2012-06-12 01:27:10 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 13 Andrius Benokraitis 2013-10-07 01:32:54 UTC 
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.