GNOME Bugzilla – Bug 658365
Fetching mail cannot be canceled
Last modified: 2012-05-06 17:56:18 UTC
I have 2 accounts in evolution, one IMAP and one POP3. For none of them I can cancel fetching mail once it was started. If you try, evo will become unresponsive. Version number of affected component: evolution-3.0.2-3.fc15.x86_64 How to reproduce: Always Steps to reproduce: 1. Set up an account in evolution 2. Fetch mail 3. Press the red icon in the stop fetching mail. Actual results: The text in the status bar changes to 'Fetching mail (canceling)', however it is not really canceled but evolution becomes unresponsive instead. The UI is blocked, all controls are greyed out and I can no longer close evolution, so I have to use --force-shutdown. Expected results: Fetching mail should be canceled and the UI should remain responsive.
Thanks for a bug report. Could you paste here a backtrace of running evolution in the frozen state, please? You can get one with a command like this: $ gdb --batch --ex "t a a bt" -pid=PID &>bt.txt where PID is a process ID of the running evolution. The resulting bt.txt file contains the information. Before you paste its content here, please make sure it doesn't contain any private information, like user names or passwords. Thanks in advance.
All I get is /usr/bin/evolution (deleted): File or directory not found.
+ Trace 228435
Thread 1 (process 4351)
I can install the debuginfo, but to me this looks like more is wrong here.
(In reply to comment #2) > All I get is > > /usr/bin/evolution (deleted): File or directory not found. I agree, thi sis pretty suspicious. Like some process would delete your /usr/bin/evolution? It sounds pretty unlikely, unless some update being done in the background.
Created attachment 197730 [details] backtrace OK, I managed to get a backtrace. Please tell me if it is helpful or if I need to install more debugsymbols. An easy way to reproduce the problem: Have evo configured to use IMAP. Then connect to a VPN and make sure it has the default route and routes all traffic. I then see "Pinging <server>" in the status bar and from that moment on neither pinging nor fetching mail can be canceled.
Thanks for the update. There doesn't seem to be installed debuginfo packages for evolution-data-server and evolution, or their version doesn't match. From this I can only see that you are using IMAP provider (not IMAP+) and that it is trying to update some folder.
Created attachment 201056 [details] new backtrace The account that is actually causing the lockup is a POP3 account. Hopefully this backtrace is better, at least you can see PO3 in there.
The relevant thread is probably this one:
+ Trace 229026
Looks like it hangs while receiving/waiting for SSL handshake response from the server.
For the record: This trace was generated with evolution-3.0.3-1.fc15.x86_64 and evolution-data-server-3.0.3-1.fc15.x86_64
Cancelling of POP3 had been improved within bug #660615, and later with commit [1]. I suppose this should behave better in 3.3.3. http://git.gnome.org/browse/evolution-data-server/commit/?id=d8b557c297
This might be fixed for both IMAP and POP3 in 3.4.0+. Please reopen, if it'll not work for you. Thanks in advance.
It has gotten better but is not quite fixed, at least not for IMAP. When I connect to or disconnect from the VPN, evolution hangs while "Pinging IMAP server..." But at least this can be canceled, so the original problem I reported is fixed.