Bug 610243 - [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)
Summary: [abrt] crash in evolution-data-server-2.30.2-2.fc13: icalcomponent_get_timezo...
Status: CLOSED DUPLICATE of bug 605891
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server   
(Show other bugs)
Version: 13
Hardware: i686 Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:976ad99dec6a1cd7df79ecf6e9f...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-01 20:08 UTC by Jan Becker
Modified: 2010-11-09 15:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 15:54:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (17.20 KB, text/plain)
2010-07-01 20:08 UTC, Jan Becker
no flags Details

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
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.

Note You need to log in before you can comment on or make changes to this bug.