Description of problem: After reporting spam, status messages about the reported message remain in the status bar. Also, evolution hangs on exit after reporting spam. Version-Release number of selected component (if applicable): evolution-rspam-0.6.0-13.fc24.x86_64 How reproducible: Always, I think. Steps to Reproduce: 1. Right-click on a spam message and seleect "Report as SPAM" 2. Note "Message reported as SPAM" and "Retrieving message ..." status messages never clear 3. Exit evolution Actual results: Evolution never exits. Clicking "close window" in the title bar generates a popup saying evo is taking a long time to exit and offering to close immediately. The close option seems to properly terminate evo. Expected results: Messages are processed, status messages clear, exiting evolution works. Additional info: This seems to happen with an Exchange EWS account and Gmail (IMAP). It doesn't seem to be an issue with POP3.
Thanks for a bug report. The Quit requests the status bar to be clear, aka no ongoing activities being running, thus when some are left there then the evolution would not quit. Could you install debuginfo packages for the evolution-data-server, evolution, evolution-ews and evolution-rspam [1], please? Catch a backtrace of the running evolution with the stuck activities, to see what the evolution does: $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt Please check the bt.txt for any private information, like passwords, email address, server addresses,... I usually search for "pass" at least (quotes for clarity only). [1] # dnf install evolution-data-server-debuginfo evolution-debuginfo \ evolution-ews-debuginfo evolution-rspam-debuginfo \ --enablerepo=*-debuginfo And make sure that the versions of the debuginfo packages match the version of the binary package.
Created attachment 1174321 [details] traceback of hung evolution process bt.txt attached, generated as described.
Thanks for the update. The backtrace shows the evolution basically idle, thus it can be that the evolution-rspam failed to finish some sub-task appropriately or something like that.
(In reply to Milan Crha from comment #3) > Thanks for the update. The backtrace shows the evolution basically idle, > thus it can be that the evolution-rspam failed to finish some sub-task > appropriately or something like that. Indeed, I can interact with Evo while it is waiting for the background task to complete. I guess the background task (in the status bar: Retrieving message ...) is what's hung. The spam report message is copied to the outbox and is either sent automatically or sent when I click Send/Receive, but the Retrieving message never clears from the status bar. What's the next step?
I can add that clicking the stop sign in the status bar message has no effect.
I found out that the activity and the message itself was leaking, thus it left at the status bar. I fixed it, together with "a little" build break, for the next version for rawhide and Fedora 24.
evolution-rspam-0.6.0-14.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-1be4d94b7a
evolution-rspam-0.6.0-14.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-1be4d94b7a
That fixed it, thanks.
evolution-rspam-0.6.0-14.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.