Bug 653715

Summary: [abrt] evolution-data-server-2.32.0-3.fc14: update_cache() at e-book-backend-exchange.c:667: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bojan Smojver <bojan>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: mbarnes, mcrha, mjs
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:d7217b06ee3b64ef7a054871924cd180fdbf9a46
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-16 07:24:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Bojan Smojver 2010-11-16 01:32:19 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
crash_function: g_type_check_instance_cast
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.6-48.fc14.i686
package: evolution-data-server-2.32.0-3.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. Just viewing e-mail.
time: 1289871006
uid: 15162
Comment 1 Bojan Smojver 2010-11-16 01:32:21 UTC 
Created attachment 460709 [details]
File: backtrace
Comment 2 Milan Crha 2010-11-16 07:24:20 UTC 
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=634971
Comment 3 Milan Crha 2011-02-10 09:47:24 UTC 
*** Bug 676487 has been marked as a duplicate of this bug. ***
Comment 4 Milan Crha 2011-06-16 07:25:44 UTC 
*** Bug 713627 has been marked as a duplicate of this bug. ***