Bug 641897 - [abrt] evolution-2.32.0-2.fc14: magazine_chain_pop_head: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.0-2.fc14: magazine_chain_pop_head: Process /usr/bin/evo...
Keywords:
Status: CLOSED DUPLICATE of bug 608163
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:db5d532077ae6986e5bec42fc20...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-11 12:59 UTC by drewskiwooskie
Modified: 2010-11-08 18:45 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (132.45 KB, text/plain)
2010-10-11 12:59 UTC, drewskiwooskie 		no flags Details
View All

Description drewskiwooskie 2010-10-11 12:59:13 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: magazine_chain_pop_head
executable: /usr/bin/evolution
kernel: 2.6.35.4-28.fc14.x86_64
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1286801447
uid: 500

comment
-----
This has not crashed before and I was not doing anything at the time except for using firefox
and listening to rhythmbox. 

How to reproduce
-----
1. I just had evolution open and I got the notification that it crashed
2.
3.
Comment 1 drewskiwooskie 2010-10-11 12:59:15 UTC 
Created attachment 452707 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:45:42 UTC 

*** This bug has been marked as a duplicate of bug 608163 ***
Comment 3 Karel Klíč 2010-11-08 18:45:42 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 #608163.

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