Bug 750391

Summary: [abrt] evolution-data-server-2.32.3-1.fc14: g_type_check_instance_cast: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: D. Wagner <daw-redhatbugzilla>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:9ab7ad6bcbc44916161f53f081a3ff1f891f6264
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-01 07:47:16 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 D. Wagner 2011-10-31 23:10:16 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 30737 bytes
cmdline: /usr/libexec/e-calendar-factory
comment: I tried the yum debuginfo suggestions, but none worked.
component: evolution-data-server
Attached file: coredump, 31875072 bytes
crash_function: g_type_check_instance_cast
executable: /usr/libexec/e-calendar-factory
kernel: 2.6.35.13-92.fc14.x86_64
package: evolution-data-server-2.32.3-1.fc14
rating: 4
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: I don't know.
time: 1319825636
uid: 10169
Comment 1 D. Wagner 2011-10-31 23:10:18 UTC 
Created attachment 531047 [details]
File: backtrace
Comment 2 Milan Crha 2011-11-01 07:47:16 UTC 
Thanks for a bug report. I see you've installed proper debuginfo packages for evolution-data-server, which is fine. I checked the upstream bugzilla and I didn't find any similar bug report, furthermore, the current upstream stable version is 3.2.1, thus the 2.32.x is considered too old for upstream, which is a reason why I'm not forwarding this there, also because of reaching end-of-life for Fedora 14. I suppose this is just a coincidence crash anyway, isn't it?