GNOME Bugzilla – Bug 751756
Endless failure loop when moving messages
Last modified: 2016-08-08 14:44:58 UTC
Created attachment 306454 [details] Example of the error messages that repeat endlessly I have some nested folders set up on my account, for example Inbox>Filed>Receipts. Geary detects and reads the contents of these folders just fine, but when I try to drag a new message into the folder, it appears to work fine, but in the logs Geary is spitting out an endless string of failure messages. Once this happens, it seems to lock up the IMAP service so while I can continue using the client, no new messages appear, and any changes I make in the client are not persisted to the server and are reset when I next start Geary. I figure there are really a couple parts to this: 1. Having the client point out that something went wrong (#713006) 2. Not letting an error of this sort throw Geary into a non-functioning state 3. Figuring out why this error happens in the first place I'm using Fastmail as my email provider, not sure if that's relevant, but maybe they're doing something strange in their IMAP that's causing this.
Oh no. When I submitted this bug I was reproducing the bug consistently. Of course, now when I went back to play with it a bit more, it has stopped reproducing, even though I'm following the same set of steps I thought were to blame. So, could be the part about nested folders is a red herring. I'll keep an eye on things and see if I can get the problem reliably again.
This could be a server issue. For now, I'm going to close this bug. But if you get it to reproduce, say so and we'll reopen it.
I've had thus happen a number more times today. The nested folders part was a red herring, I have now had the same error take place on other single-level moves, and when moving messages to the Trash. I haven't yet figured out a specific set of steps to cause it to happen, but it seems that if I use Geary for a little while it will crop up pretty reliably after a certain amount of use. So if there's more debugging I can do to help you diagnose, please let me know what to do.
The network side is not my area of expertise, but if you could run geary with --debug --log-network and get some of the output just before this begins, it may help.
Created attachment 306719 [details] Full log + network log from bug occurrence Here's a full log with --log-network from startup until encountering the bug. It's a bit long, but it should be obvious where the bug happened due to the endlessly repeating log messages.
Any news on this? I'm still seeing this problem frequently, so if you need more debugging information, I can certainly dig it up for you if you tell me where to look. It's a shame; I'd really like to be using Geary for daily use, but this bug makes it a no-go for me.
(In reply to Ian Young from comment #6) > Any news on this? I'm still seeing this problem frequently, so if you need > more debugging information, I can certainly dig it up for you if you tell me > where to look. Ian, since you are using Fastmail, who use Cyrus as their IMAO software, this issue was probably fixed in Geary 0.11 as part of Bug 757166. As such I'm going to mark this as a duplicate. Please try out Geary 0.11 and if it is still a problem for you, then do reopen this bug and I'll take a look at it. *** This bug has been marked as a duplicate of bug 757166 ***