Bug 620340

Summary: [abrt] crash in evolution-2.30.2-4.fc13: raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Steven Bakker <sb>
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: x86_64   
OS: Linux   
Whiteboard: abrt_hash:115f256162c724e370b81b7a8cf7169c88ae96e1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 13:30:28 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 Steven Bakker 2010-08-02 09:02:50 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 115f256162c724e370b81b7a8cf7169c88ae96e1
kernel: 2.6.33.6-147.fc13.x86_64
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)

comment
-----
Went to the calendar view, clicked on a few consecutive dates. I am subscribed to two external (webcal) calendars and have two local calenders, one of which I publish over webdav.

(Calendaring in evolution has been unstable for a while now. Clicking on meeting invitations in email usually crashes evolution as well.)

How to reproduce
-----
1. Open evolution.
2. Go to calendar view.
3. Click on various (consecutive) dates.
Comment 1 Steven Bakker 2010-08-02 09:02:52 UTC 
Created attachment 435977 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:30:28 UTC 

*** This bug has been marked as a duplicate of bug 629252 ***
Comment 3 Karel Klíč 2010-11-09 13:30:28 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 #629252.

Sorry for the inconvenience.