Bug 627135 - [abrt] 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] evolution-data-server-2.30.2-2.fc13: magazine_chain_pop_head: Process ...
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:e88e2bfab0e6a2ce38fd0a8111d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-25 07:30 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:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (55.22 KB, text/plain)
2010-08-25 07:30 UTC, James Heather
no flags Details

Description James Heather 2010-08-25 07:30:14 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
crash_function: magazine_chain_pop_head
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: evolution-data-server-2.30.2-2.fc13
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: Seemed to be a crash of a Google contacts address book, during suspend/resume.
time: 1282681301
uid: 500

Comment 1 James Heather 2010-08-25 07:30:16 UTC
Created an attachment (id=440847)
File: backtrace

Comment 2 Karel Klíč 2010-11-08 18:16:47 UTC

*** This bug has been marked as a duplicate of bug 595963 ***

Comment 3 Karel Klíč 2010-11-08 18:16:47 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.