Bug 736405

Summary: [abrt] evolution-data-server-2.32.2-1.fc14: g_atomic_int_get: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Andrew Kornak <akornak>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:82968145754d1c394ef0dab2047b00b2e646c065
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-08 09:05:43 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 Andrew Kornak 2011-09-07 15:40:29 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 15852 bytes
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
Attached file: coredump, 27545600 bytes
crash_function: g_atomic_int_get
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.14-95.fc14.i686
package: evolution-data-server-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1315409824
uid: 500

How to reproduce
-----
1. clicked on contacts in evolution
2. address book crashed
3.

Comment 1 Andrew Kornak 2011-09-07 15:40:32 UTC
Created attachment 521926 [details]
File: backtrace

Comment 2 Milan Crha 2011-09-08 09:05:43 UTC
Thanks for a bug report. Based on the backtrace I suppose this crashed because one of your contact doesn't contain only valid UTF8 letters, thus the GVariant crashes on it. There was done a fix for this, which is included in evolution-data-server 3.0.0. I'm marking this as a duplicate of bug #693225.

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