GNOME Bugzilla – Bug 520526
should cancel imap mailbox summary update when closed
Last modified: 2021-05-19 11:57:08 UTC
Using the current 2.21 version, when evolution is scanning for changed messages in an imap mailbox and you close it the interface is unsensitived and the update is not stopped, if you are on a slow connection it might take quite some time to get the update and since the interface is not available you can't switch to offline mode to workaround the issue. That's especially an issue when you get network issues and the update is blocked on timeout
Created attachment 106624 [details] [review] proposed eds patch for evolution-data-server; consider something like this.
the change seems to work in some cases but not always when it's refreshing folders or doing several actions. switching to not-connected works immediatly, could that be used when closing?
Hmm, I found that when forcing offline, mail component calls mail_cancel_all (); which forces cancel for all camel threads. This function is also called in next stage of the quit process, but before that it is waiting to finish its job. Definitely cancel some operations in its middle is not the best thing. (I know, in such operations is cancellation blocked - or should be at least.) I will rather try to update my patch on IMAP only, I've such a feeling it will be better.
Created attachment 106720 [details] [review] proposed eds patch ][ for evolution-data-server; Updated patch, I also found an issue with the last one, the store's connect_lock could stay locked, so fixing this too. I see one weak point on your workaround, I think, if you do go-offline and your changes in actual folder had not been saved yet, then the next time the summary on the server will be different from the local, hard to say whether the local and/or remote summary was updated at all. (Because it was really canceled in the middle of downloading changes.) I added something similar to this patch too, though. :)
Bumping version to a stable release.
Milan, I think anyways the server thing will be downloaded and matched against local, the chances of loss is nill. You can commit to trunk/stable
Committed to trunk. Committed revision 8588. Committed to gnome-2-22. Committed revision 8589. Only one note, I committed the updated patch, not the first one you marked as accepted :)
Reopening, I notices that even I quit the application, then it still downloads info of the messages in a folder. It doesn't do that every time, but from time to time it does. For big folders, like +20000 messages it can take unbelievable time to quit. I do quit in time of initial folder update after start.
Confirming that evolution takes several minutes to exit here, in 2.28.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new bug report ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.