Bug 614429 - [abrt] crash in evolution-2.30.2-1.fc13: magazine_chain_pop_head: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.2-1.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: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c456eadfc7b72307c2a45f3dab5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-14 13:34 UTC by Peter Green
Modified: 2010-11-08 18:44 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:44:40 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (58.33 KB, text/plain)
2010-07-14 13:34 UTC, Peter Green 		no flags Details
View All

Description Peter Green 2010-07-14 13:34:30 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: Simply attempted to compose a new message.
component: evolution
crash_function: magazine_chain_pop_head
executable: /usr/bin/evolution
global_uuid: c456eadfc7b72307c2a45f3dab5b03da2a1f81a3
kernel: 2.6.33.6-147.fc13.x86_64
package: evolution-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Switched back to Evolution (it was on another virtual desktop)
2. Clicked the "New Message" context button on the toolbar
3. Evolution froze and then crashed.
Comment 1 Peter Green 2010-07-14 13:34:37 UTC 
Created attachment 431772 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:44:40 UTC 

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