Bug 610243

Summary: [abrt] crash in evolution-data-server-2.30.2-2.fc13: icalcomponent_get_timezone: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jan Becker <Jan.Becker2>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:976ad99dec6a1cd7df79ecf6e9f8e512d7ff2d7a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 15:54:40 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 Jan Becker 2010-07-01 20:08:54 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-calendar-factory
comment: only after this procedure the calendar data is available
component: evolution-data-server
crash_function: icalcomponent_get_timezone
executable: /usr/libexec/e-calendar-factory
global_uuid: 976ad99dec6a1cd7df79ecf6e9f8e512d7ff2d7a
kernel: 2.6.33.5-124.fc13.i686.PAE
package: evolution-data-server-2.30.2-2.fc13
rating: 4
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. started evolution, no calendar data available
2. entered a new appointment
3. tried to save - crash (evolution still running)

Comment 1 Jan Becker 2010-07-01 20:08:56 UTC
Created attachment 428545 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:54:40 UTC

*** This bug has been marked as a duplicate of bug 605891 ***

Comment 3 Karel Klíč 2010-11-09 15:54:40 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 #605891.

Sorry for the inconvenience.