Bug 609670 - [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:e5d2ce9d78430da7475e30899ac...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-30 19:55 UTC by Maik Strewe
Modified: 2010-11-08 18:44 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (88.32 KB, text/plain)
2010-06-30 19:55 UTC, Maik Strewe 		no flags Details
View All

Description Maik Strewe 2010-06-30 19:55:16 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/evolution
comment: using evolution in kde enviroment
component: evolution
crash_function: magazine_chain_pop_head
executable: /usr/bin/evolution
global_uuid: e5d2ce9d78430da7475e30899acb480ac4692acc
kernel: 2.6.33.5-124.fc13.i686
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.evolution running since 2 days for instant email acces
2.want to write an email. use the short-cut (up-left button) to get the write email context
3.forced close
Comment 1 Maik Strewe 2010-06-30 19:55:25 UTC 
Created attachment 428081 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:44:26 UTC 

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