Bug 712285

Summary: [abrt] evolution-2.28.3-24.el6: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: Red Hat Enterprise Linux 6 Reporter: Siddharth <swaikar>
Component: evolution-mapiAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: jwest, vgaikwad
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-25 19:18:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Backtrace, Dissassembly none

Description Siddharth 2011-06-10 06:17:28 UTC 
Description of problem:

abrt version: 1.1.16
Attached file: backtrace, 32572 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 180273152 bytes
executable: /usr/bin/evolution
kernel: 2.6.32-71.el6.x86_64
rating: 1
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Attached file: sosreport.tar.xz, 871976 bytes
time: 1307539646
uid: 500
Customer comment 
1. Using an Microsoft Exchange account (MAPI on evolution)
2. Attempted to move several emails from inbox to a different folder both by dragging or by selecting, right-click then


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Workstation release 6.1 (Santiago)
evolution-2.28.3-24.el6
architecture: x86_64

How reproducible:
random crash

Steps to Reproduce:
1.
2.
3.
  
Actual results:
evolution killed

Expected results:
evolution should not killed

Additional info:
Comment 2 Siddharth 2011-06-10 06:31:08 UTC 
Created attachment 504022 [details]
Backtrace, Dissassembly
Comment 3 RHEL Program Management 2011-07-06 01:04:55 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. If you would like it considered as an
exception in the current release, please ask your support
representative.