Bug 608926 - [abrt] crash in evolution-2.30.1-8.fc13: magazine_chain_pop_head: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.1-8.fc13: magazine_chain_pop_head: Process /us...
Keywords:
Status: CLOSED DUPLICATE of bug 608163
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:80363a2ff6de5ef1648e82fbd79...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-28 23:05 UTC by Glen Fullmer
Modified: 2010-11-08 18:44 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (81.47 KB, text/plain)
2010-06-28 23:05 UTC, Glen Fullmer 		no flags Details
View All

Description Glen Fullmer 2010-06-28 23:05:33 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
comment: Wasn't doing anything when it crashed. It was open but the machine had been without keyboard or mouse input for at least 50 minutes before it crashed.
component: evolution
crash_function: magazine_chain_pop_head
executable: /usr/bin/evolution
global_uuid: 80363a2ff6de5ef1648e82fbd79d67bc77d75317
kernel: 2.6.33.5-124.fc13.i686.PAE
package: evolution-2.30.1-8.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Unknown
2.
3.
Comment 1 Glen Fullmer 2010-06-28 23:05:38 UTC 
Created attachment 427524 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:44:17 UTC 

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