Bug 681724 - [abrt] evolution-data-server-2.91.6-4.fc15: g_mutex_free_posix_impl: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT)
Summary: [abrt] evolution-data-server-2.91.6-4.fc15: g_mutex_free_posix_impl: Process ...
Keywords:
Status: CLOSED DUPLICATE of bug 663402
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:dc4bd107c1e6953ff6d3552bed6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-03 03:00 UTC by John Paul Adrian Glaubitz
Modified: 2011-03-03 07:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-03 07:20:40 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (23.67 KB, text/plain)
2011-03-03 03:00 UTC, John Paul Adrian Glaubitz 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description John Paul Adrian Glaubitz 2011-03-03 03:00:43 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 24240 bytes
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
Attached file: coredump, 36274176 bytes
crash_function: g_mutex_free_posix_impl
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.38-0.rc6.git6.1.fc15.x86_64
package: evolution-data-server-2.91.6-4.fc15
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1299120618
uid: 500

How to reproduce
-----
1. Start Evolution the first time after installing Fedora 15.
2. Setup accounts for GMail and Hotmail, Hotmail is setup to leave messages on the server. Otherwise default settings.
3. Receive emails several times.
4. Close Evolution, wait a few seconds.
5. Startup Evolution

This is not necessarily a way to reproduce this crash. I merely describe what things I did before the crash occurred. It might just be totally unrelated.
Comment 1 John Paul Adrian Glaubitz 2011-03-03 03:00:47 UTC 
Created attachment 481983 [details]
File: backtrace
Comment 2 Milan Crha 2011-03-03 07:20:40 UTC 
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate. It's from another backend, but the cause is the same, from my point of view.

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