Bug 704411 - [abrt] evolution-data-server-2.32.2-1.fc14: g_variant_is_trusted: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.2-1.fc14: g_variant_is_trusted: Process /us...
Keywords:
Status: CLOSED DUPLICATE of bug 656814
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:64d9eb7afeba95999076c03b566...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-13 03:45 UTC by Slawek Gawlowski
Modified: 2011-05-13 06:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-13 06:17:15 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (12.56 KB, text/plain)
2011-05-13 03:45 UTC, Slawek Gawlowski 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Slawek Gawlowski 2011-05-13 03:45:31 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 12859 bytes
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
Attached file: coredump, 37011456 bytes
crash_function: g_variant_is_trusted
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.13-91.fc14.x86_64
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)
How to reproduce: adding contacts detaisl from one adress book to another
time: 1305257799
uid: 500
Comment 1 Slawek Gawlowski 2011-05-13 03:45:38 UTC 
Created attachment 498680 [details]
File: backtrace
Comment 2 Milan Crha 2011-05-13 06:17:15 UTC 
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

*** This bug has been marked as a duplicate of bug 656814 ***
Note You need to log in before you can comment on or make changes to this bug.