Bug 613469 - [abrt] crash in evolution-data-server-2.30.2-2.fc13: magazine_chain_pop_head: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-data-server-2.30.2-2.fc13: magazine_chain_pop_head:...
Keywords:
Status: CLOSED DUPLICATE of bug 595963
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2e0aa30df13a55c17bd931290b4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-11 21:59 UTC by James Heather
Modified: 2010-11-08 18:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:16:32 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (50.31 KB, text/plain)
2010-07-11 21:59 UTC, James Heather 		no flags Details
View All

Description James Heather 2010-07-11 21:59:42 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/e-addressbook-factory
comment: Wasn't doing anything... I think it crashed when it tried to sync my Google contacts.
component: evolution-data-server
crash_function: magazine_chain_pop_head
executable: /usr/libexec/e-addressbook-factory
global_uuid: 2e0aa30df13a55c17bd931290b4df2e4a32cf9db
kernel: 2.6.33.6-147.fc13.x86_64
package: evolution-data-server-2.30.2-2.fc13
rating: 3
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 James Heather 2010-07-11 21:59:45 UTC 
Created attachment 431029 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:16:32 UTC 

*** This bug has been marked as a duplicate of bug 595963 ***
Comment 3 Karel Klíč 2010-11-08 18:16:32 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #595963.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.