I tried choosing the message search box to 'body contains' and Evolution just seems to get stuck. The status bar says 'Retrieving message 10390', but it just stands there. I tried pressing the cancel button associated with the Retrieving message item, but that also just hangs there. Attaching screenshot. Also switched search back to 'sender contains' without that solving the problem. The issue now is that while the UI is responsive in a way, there is no way to view any messages anymore as it just seems stuck with a 'Getting messages' note. And anything I do just seems to collate down on the status bar without actually moving forward.
Created attachment 714454 [details] Image of 'hung' Evolution
Thanks for a bug report. I suppose this is 3.6.4 of eds/evo, right? I just tried the git master (close to 3.8.0) and it works fine for me. With Zimbra advertising server side searches, and IMAPX finally capable of server-side searching, the search is quick and doesn't download message during the search. On the other hand, I think there could happen similar issues, maybe still in git master, but it depends on actual backtrace. Could you install debuginfo packages for evolution-data-server and evolution, make sure they'll be of the same version as your binary packages. Then reproduce the deadlock (I guess it's something like deadlock between threads), then get a backtrace of running evolution process, please? You can get the backtrace with command like this: # $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt only make sure the file will not contain any private information, like passwords, email addresses and/or server addresses you would not like to share in public (I usually search for "pass" in the file (quotes for clarity only)).
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.