Bug 606791 - [abrt] crash in evolution-2.30.1-8.fc13: is_online: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.1-8.fc13: is_online: Process /usr/bin/evolutio...
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:06617740a3bc3b66807f469b6ad...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-22 14:03 UTC by Nathan Crubel
Modified: 2011-06-13 18:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-13 18:16:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (56.19 KB, text/plain)
2010-06-22 14:03 UTC, Nathan Crubel
no flags Details

Description Nathan Crubel 2010-06-22 14:03:23 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution
comment: It just fails on me while fetching emails.
component: evolution
crash_function: is_online
executable: /usr/bin/evolution
global_uuid: 06617740a3bc3b66807f469b6ad25e7c9083d64b
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. Open Evolution
2. Let it get all the emails

Comment 1 Nathan Crubel 2010-06-22 14:03:25 UTC
Created attachment 425932 [details]
File: backtrace

Comment 2 Nathan Crubel 2010-06-29 19:33:36 UTC
Have not had any problems since upgrading today to 2.30.2-1.  Will know more in the next couple of days if it keeps crashing.  Somedays it would crash about 4 -5 times in a row and over 10 times a day.

Comment 3 Bug Zapper 2011-06-01 15:55:25 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 4 Nathan Crubel 2011-06-13 18:16:58 UTC
No longer running Fedora 13.  Seemed to have been a problem with evolution and exchange server I was connecting too.  I have no information as it started working fine.

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