Bug 639385

Summary: [abrt] evolution-data-server-2.32.0-1.fc14: e_intervaltree_search: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Don Church <donchurch>
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: bugzilla, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:79f4f2651f32e322460b7c70c45b8510ee6b1592
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 09:32:47 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 Don Church 2010-10-01 15:51:14 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-calendar-factory
component: evolution-data-server
crash_function: e_intervaltree_search
executable: /usr/libexec/e-calendar-factory
kernel: 2.6.35.4-28.fc14.i686.PAE
package: evolution-data-server-2.32.0-1.fc14
rating: 4
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1285948268
uid: 500

How to reproduce
-----
1.click clock to open calender
2.
3.

Comment 1 Don Church 2010-10-01 15:51:16 UTC
Created attachment 451045 [details]
File: backtrace

Comment 2 malak 2010-11-07 23:52:06 UTC
I just installed F14; clicking the evolution email icon at the top, it immediately crashes.

Package:    	evolution-2.32.0-2.fc14
Latest Crash:	Sun 07 Nov 2010 06:47:55 PM 
Command:    	evolution
Reason:     	Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Comment:    	None
Bug Reports:

Comment 3 Milan Crha 2010-11-08 09:32:47 UTC

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