Bug 701364 - [abrt] evolution-data-server-2.32.2-1.fc14: g_mutex_free_posix_impl: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-data-server-2.32.2-1.fc14: g_mutex_free_posix_impl: Process ...
Keywords:
Status: CLOSED DUPLICATE of bug 701077
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:db406e17364fb954ffad6c6c86b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-02 17:30 UTC by John Reiser
Modified: 2011-05-03 06:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-03 06:04:31 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (23.59 KB, text/plain)
2011-05-02 17:30 UTC, John Reiser 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description John Reiser 2011-05-02 17:30:15 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 24160 bytes
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
Attached file: coredump, 36466688 bytes
crash_function: g_mutex_free_posix_impl
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.12-90.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 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1304343701
uid: 500

How to reproduce
-----
1. shortly after login; cause unknown; user invoked Thunderbird 3.1.10, but "e-addressbook-factory" is unknown to the user
2.
3.
Comment 1 John Reiser 2011-05-02 17:30:17 UTC 
Created attachment 496314 [details]
File: backtrace
Comment 2 Milan Crha 2011-05-03 06:04:31 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 701077 ***
Note You need to log in before you can comment on or make changes to this bug.