Red Hat Bugzilla – Bug 863236
evolution couldn't close
Last modified: 2014-02-05 07:27:16 EST
Created attachment 621804 [details]
Description of problem:
evolution couldn't close
Created attachment 621806 [details]
Evolution backtrace 2
$ rpm -qa | grep evolution | sort
Created attachment 621808 [details]
Created attachment 622655 [details]
Evolution backtrace 3
Created attachment 622656 [details]
Thanks for a bug report. I see in the backtraces that one thread is searching for a contact photo of the message you selected, waiting for a response from the evolution-addressbook-factory, which blocks the other threads, also trying to search for contact's photo. It's OK to block other threads, but it's not OK to wait for the addressbook factory response that long. The evolution won't quit, because it requires all contact photo requests being finished.
Could you get a backtrace of running evolution-addressbook-factory, please? There should be shown what it is waiting for/trying to do. Thanks in advance.
I also see long waits (over 2 minutes for my current opened app to close and still waiting) for evolution to close, or not at all, whether there was an error or not. Now, after reading above, I went back into my preferences and unchecked "show photograph" of emails from users. Went to close it and still waiting. Going to kill it and then reopen and see if has any issues with that preference unchecked (for now). And after reopening evolution again, and then closing, it waited a bit (didn't time it, but was def under a minute) but it did close this time.
BTW, all I do with evolution or was doing this time around, was just clicking on emails and previewing emails, not even opening nor replying to any at the moment.
AND it's on KDE (I don't use gnome itself).
[mike@scrappy ~]$ rpm -qa |grep evolution
Also, is this related to..
(In reply to comment #8)
> Also, is this related to..
Maybe, I'm still not sure. It seems to me that the common part is the status bar, being full of pending actions. The backtrace from comment #4 shows the main thread repainting a window. If I recall correctly, the CPU usage is also higher than usually. That all can be related or not, though the redraws and higher CPU usage is probably caused by the spinner redraw. I have a test application, which emulates it too, though it doesn't have influence on parts I would expect, like delivery of an idle callback.
Still takes a bit to close but so far does indeed close though. And no bugs like I was getting when had the photograph options turned on, whereas with that option off, no crashes as of yet.
I have the same problem, most of the time evolution bar is full of pending action and won't close, that's painfully anoying when you use it everyday to have to kill the process to quit. And it make my notebook heat a lot ...
There were done changes for 3.6.4 which should (fully or partially) address this issue. The date for a release is not set yet, but I guess it'll be done within a week or two.
I still got the problem, I am still not able to close my evolution, all widgets in the window are desactivated but the window stay. It has been month now that this problem exist...
It is VERY frustrating.
Maël, did you update to 3.6.4 of (all) evolution package(s)?
Yes I have a fedora 18 setup fully updated, Evolution is version 3.6.4
OK, thanks. I thought it's like updating only evolution, but not evolution-data-server, but as you have the machine fully updated, then that's OK. One possible thing would be bug #953641. Could you try to downgrade gcr and do the other steps as described in that bug report?
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.
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 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.