Bug 688230 - [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 663402
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:6f8509cac4bf1b5d6ddf16c363f...
: 688416 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-16 15:49 UTC by Jobst Hoffmann
Modified: 2011-03-17 09:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-17 09:39:55 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (22.65 KB, text/plain)
2011-03-16 15:49 UTC, Jobst Hoffmann 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jobst Hoffmann 2011-03-16 15:49:48 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 23197 bytes
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
Attached file: coredump, 76136448 bytes
crash_function: g_mutex_free_posix_impl
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.11-83.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: 1300290323
uid: 10637

How to reproduce
-----
1. booted/started the computer
2. logged in to my account
3. after a short time the crash happened (I did nothing specific with evolution
Comment 1 Jobst Hoffmann 2011-03-16 15:49:50 UTC 
Created attachment 485770 [details]
File: backtrace
Comment 2 Milan Crha 2011-03-17 09:39:55 UTC 
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate.

The bug is similar because it crashes in the same function, only under different circumstances, though the reason seems to be same. The book backend is freed in one thread, while other thread is still working with it.

*** This bug has been marked as a duplicate of bug 663402 ***
Comment 3 Milan Crha 2011-03-17 09:43:32 UTC 
*** Bug 688416 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.