Bug 467417 - Bug in glib causes evolution to crash occasionally.
Summary: Bug in glib causes evolution to crash occasionally.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: glib2
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL: http://bugzilla.gnome.org/show_bug.cg...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-17 11:29 UTC by Jason Smith
Modified: 2009-07-14 14:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-14 14:29:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jason Smith 2008-10-17 11:29:50 UTC
Description of problem:
I submitted a bug report using the Gnome Bug Tool when evolution crashed and was pointed to this bugzilla report which contains a patch for glibc that they think might fix it:

http://bugzilla.gnome.org/show_bug.cgi?id=523463

If it is appropriate, can this patch be added to a future bugfix release in Fedora?

Version-Release number of selected component (if applicable):
evolution-2.22.3.1-1.fc9.x86_64
glib-1.2.10-29.fc9.x86_64

How reproducible:
It is very difficult to reproduce, only happens occasionally when reading html formatted email messages.

Comment 1 Rex Dieter 2008-10-17 11:35:23 UTC
Reassigning -> glib2

Comment 2 Jason Smith 2008-10-17 21:14:24 UTC
Sorry about the glib2 mixup, as you probably know, Fedora 9 has:

glib2-2.16.6-1.fc9.x86_64

FYI, I noticed that this patch was included in GLib 2.18.1:

http://mail.gnome.org/archives/gnome-announce-list/2008-September/msg00084.html

I don't know if it is worth fixing it in Fedora 9, but at least try for Fedora 10.  I noticed that the RawHide/Beta from a few weeks ago still has only glib2-2.18.0 in it.

~Jason

Comment 3 Joshua Rosen 2009-01-13 15:44:21 UTC
I've been getting Evolution hangs in both F9 and F10. I have Evolution open at all times, after a number of hours, or maybe a day, it will be completely unresponsive and the only solution is to kill it. Unfortunately it's not leaving any clues about what is causing the crashes. However it is happening on different machines, one running F10 and one running F9.

Comment 4 Bug Zapper 2009-06-10 02:59:53 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 '9'.

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

Comment 5 Bug Zapper 2009-07-14 14:29:30 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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