Bug 625111

Summary: [abrt] evolution-2.30.2-4.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: mark <mswaggard>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:2c3b9897579f081e99cb3585aac548ee18698ef7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 14:19:19 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
File: backtrace none

Description mark 2010-08-18 15:57:36 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: evolution
comment: I tried using evolution connected ot the company exchange server, evolution crashes a lot. trying to submit as much as possible so someone can fix evolution. 
component: evolution
crash_function: raise
executable: /usr/bin/evolution
kernel: 2.6.33.6-147.2.4.fc13.i686
package: evolution-2.30.2-4.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1282146358
uid: 500

How to reproduce
-----
1. open evolution that is connected to MS exchange server
2. open emails, calendar events, ...etc
3. use evolution for 20 mins conneced to exchange server.  it will crash within this amount of time if doing any real work.
4. submit as many tickets as possible since this software is still running like an alpha
Comment 1 mark 2010-08-18 15:57:38 UTC 
Created an attachment (id=439421)
File: backtrace
Comment 2 Karel Klíč 2010-11-09 14:19:19 UTC 

*** This bug has been marked as a duplicate of bug 618331 ***
Comment 3 Karel Klíč 2010-11-09 14:19:19 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #618331.

Sorry for the inconvenience.