Red Hat Bugzilla – Bug 471956
crashes and hangs with evolution 18.104.22.168
Last modified: 2009-12-18 01:52:15 EST
Since the upgrade to 22.214.171.124, I've been experiencing crashes and hangs with evolution. The crashes almost always happen when either selecting all messages in a folder or expunging a folder. Evolution just vaporizes with no error messages. I've been running with CAMEL_VERBOSE_DEBUG on and it doesn't show anything helpful in the .xsession-errors file. I've also experienced complete lockups, again usually when expunging a folder.
I don't know if it helps but none of these problems occurred with just 2.24.1.
CTRL-A,CTRL-D,CTRL-E very quickly is one way to make it happen semi-regularly.
I'm seeing very similar errors with evolution on F-10 with evolution-exchange
I'm running the following versions
$ rpm -qa| grep evolution
I have a backtrace but without all the debuginfo installed so I'll attach it for reference and will install all the debuginfo packages I think it needs to see if I can't get more details.
Created attachment 323898 [details]
Initial backtrace of evolution / evo-exchange
Created attachment 323942 [details]
full evolution bt when running through gdb
The attached file has a full backtrace with all the debuginfo packages installed when running through gdb. Once I got the segfault I did a "thread apply all bt" and the full run output is in the attached file.
I noticed that since the glibc update on Monday, evolution always segfaults when I quit. This is on three different systems running rawhide. On my system with an nfs mounted home directory, I just had it totally break evolution. It would start back up but never present a window. The last thing in the printed to the screen with verbose debug set was this:
DB SQL operation [PRAGMA cache_size=100] started
Camel SQL Exec:
I had to blow away the .evolution/mail/imap/<account>/folders.db to get evolution to work again.
Thanks for the bug report. I looked to the upstream bugzilla and found one bug with very similar trace, only the circumstances are a bit different (reporter there only opens Evolution). I'll use the upstream bug  to track this problem.
(In reply to comment #5)
> I noticed that since the glibc update on Monday, evolution always segfaults
> when I quit. This is on three different systems running rawhide. ...
Thomas, can you file a separate bug for your issue, with a gdb trace like in comment #4 when Evolution crashes/freezes, so we can try to find where is the problem? Thanks in advance.
Please don't close this bug until its actually fixed in Fedora. In the very least it gives a bug to assign dupes to and for people to find and search against.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
This seems a lot more stable for me with evolution 2.24.2. Anyone else see improvements?
I still see hangs but most of them seem to eventually recover if I wait long enough (30-90 seconds).
The 2.24.2 release has mostly fixed my issues. Thomas I'll leave you to decide when you want to close the bug if its fixed your issue or not.
There are still crashes, even with the latest version 2.24.2-2.fc10. For instance, viewing of some inline attachments will cause it to crash. Also, when connecting to exchange, it often hangs.
(In reply to comment #12)
> There are still crashes, even with the latest version 2.24.2-2.fc10. For
> instance, viewing of some inline attachments will cause it to crash.
Can you file some bug for this, the best with some sample mail with which you can reproduce it reliably? Feel free as a private bug and/or with stripped private information, of course.
> Also, when connecting to exchange, it often hangs.
Can you install debug info packages for evolution, evolution-data-server, evolution-exchange, gtkhtml3 and create a bug with a stack trace of the hang Evolution? I would like to look at it, but it requires more detailed information.
Thanks in advance, for both.
Is this problem still present with the latest Fedora 10 updates?
I don't recall seeing any non recovered hangs recently though I've grown more patient as Evolution can be quite slow at times.
Is this an issue still?
I've moved to Fedora 11 Beta and things are largely the same. No crashes but general interface lockups that eventually recover. Every once in a while, it hangs completely but it happens to rarely that I can't discern a pattern. It is also still quite slow.
The speed issue may be improved by running
Thanks for that. It does seem to have improved the speed quite a bit. Would putting this in a crontab to run each night be recommended?
Each night might be a little excessive. Maybe weekly or monthly. We're working on getting that to run automatically in the background without tying up the whole application.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.