Bug 669718 - [abrt] evolution-data-server-2.32.1-1.fc14: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.1-1.fc14: Process /usr/libexec/e-calendar-f...
Keywords:
Status: CLOSED DUPLICATE of bug 650538
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:148e61d326007669952b0f046e8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-14 14:17 UTC by Jens Hansen
Modified: 2011-01-14 15:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-01-14 15:43:50 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (38.05 KB, text/plain)
2011-01-14 14:17 UTC, Jens Hansen 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.