Bug 669718

Summary: [abrt] evolution-data-server-2.32.1-1.fc14: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jens Hansen <jhansen>
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: 14CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:148e61d326007669952b0f046e83cad8b9178b8c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-14 15:43:50 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
File: backtrace none

Description Jens Hansen 2011-01-14 14:17:42 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/e-calendar-factory
component: evolution-data-server
crash_function: icaltimezone_load_builtin_timezone
executable: /usr/libexec/e-calendar-factory
kernel: 2.6.35.10-74.fc14.x86_64
package: evolution-data-server-2.32.1-1.fc14
rating: 4
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295006295
uid: 500

comment
-----
questo errore è ripetibile aggiungendo nuovi calendari gmail a evolution

How to reproduce
-----
1.ho aggiunto un calendario gmail a evolution
2.duranta lo scaricamento del calendario è avvenuto il crash
3.
Comment 1 Jens Hansen 2011-01-14 14:17:46 UTC 
Created attachment 473529 [details]
File: backtrace
Comment 2 Milan Crha 2011-01-14 15:43:50 UTC 
Thanks for a bug report. A very similar one had been filled already, thus I'm marking this as a duplicate. It'll be great if you could write comments and reproducer steps in English next time.

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