Bug 620517 - [abrt] crash in evolution-2.30.2-4.fc13: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.2-4.fc13: Process /usr/bin/evolution was kille...
Status: CLOSED DUPLICATE of bug 624813
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:33cdf6dde8c731ee20dc093b92d...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-02 18:36 UTC by Brian Wheeler
Modified: 2010-11-09 14:02 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2010-11-09 14:02:17 UTC

Attachments (Terms of Use)
File: backtrace (38.60 KB, text/plain)
2010-08-02 18:36 UTC, Brian Wheeler
no flags Details

Description Brian Wheeler 2010-08-02 18:36:09 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: I've got two imap accounts and when evolution sits idle for a while it will crash.  The version with F12 didn't do this.  One account is attaching to cyrus and the other to exchange.  The check for new mail refresh is set to every minute.
component: evolution
executable: /usr/bin/evolution
global_uuid: 33cdf6dde8c731ee20dc093b92d476fa387590e6
package: evolution-2.30.2-4.fc13
rating: 3
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1.  Nothing.  Let evolution sit idle for a while and check email
2.  sometimes it will just crash
3.  restart it

Comment 1 Brian Wheeler 2010-08-02 18:36:13 UTC
Created attachment 436090 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:02:17 UTC

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

Comment 3 Karel Klíč 2010-11-09 14:02: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 #624813.

Sorry for the inconvenience.

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