Bug 683542

Summary: [abrt] evolution-2.91.6.2-1.fc15: e_icon_factory_get_icon: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: James Lambert <jms.lambert>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f37b7453101a72572841476280d5272199e8aa61
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 17:03:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description James Lambert 2011-03-09 16:43:59 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 57479 bytes
cmdline: evolution
comment: I have 4 Google calendars loaded
component: evolution
Attached file: coredump, 138981376 bytes
crash_function: e_icon_factory_get_icon
executable: /usr/bin/evolution
kernel: 2.6.38-0.rc8.git0.1.fc15.x86_64
package: evolution-2.91.6.2-1.fc15
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1299688185
uid: 500

How to reproduce
-----
1. Started Evolution
2. Hit Calendar button
3.

Comment 1 James Lambert 2011-03-09 16:44:02 UTC
Created attachment 483259 [details]
File: backtrace

Comment 2 Milan Crha 2011-03-10 07:24:43 UTC
Thanks for a bug report. Could you run evolution from console and paste here the message with an explanation why this crashed, please? Abrt is still not able to get these :( Thanks in advance.

Comment 3 James Lambert 2011-03-10 10:07:41 UTC
Hi, I've just been trying to reproduce this running evolution from the console with no luck so it looks like it was just a one off. If I manage to reproduce the issue I'll update here.

Comment 4 Milan Crha 2011-03-10 15:15:59 UTC
Thanks for giving it a try. I think the ~/.xsession-errors file contains those warnings when the application crashes (supposing it printed something, which in your case it did), so you can safely run evolution as before and when it crashes then examine the file content (its end) to see whether there is anything from evolution.

I'm setting this to need-info, to have some facility of auto-closing for cases when you'll not be able to reproduce this again.

Comment 5 Fedora End Of Life 2012-08-07 17:03:27 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping