GNOME Bugzilla – Bug 748548
Geary detects new messages, but does not download them unless restarted
Last modified: 2018-02-07 06:29:20 UTC
Next to my inbox, I have the little icon showing that their are new messages, but they don't show up in my conversation view unless I restart geary. I'm using IMAP + davmail (for owa ews). I've got debug from when this happens. This consistently broken. No messages load until I've restarted geary.
Created attachment 302474 [details] debug
This looks similar to bug 714779. Not sure if they're related.
*** Bug 748547 has been marked as a duplicate of this bug. ***
I'm not sure if we've ever had Geary working with davmail. Bug 714778 asks for support, but I'm not sure if that means connecting to davmail or integrating it within Geary. Do you get an indication of new messages in the conversation list (the middle pane of the three pane view)?
I see the new mail symbol (the little numbers) in the far left pane, but nothing in the middle pane. I also don't get the new mail popup message. Everything comes through just fine as soon as I restart geary though.
Well, regarding Bug 714778, I'd say it's clear that geary is MOSTLY working with davmail already. I'm using it to get Exchange email.
Thanks for the clarification. Not having looked that this part of the IMAP code, I believe Geary gets a notification from the server that this is new mail. At this point, I think it updates the unread count in the folder list. It then queries the server to actually get the mail, which is added to the conversation list and (if relevant) the conversation view. It sounds like that second step isn't being taken, though I can't tell you why offhand. If you switch folders and the return to the inbox, does that trigger the new mail to be loaded?
No, switching folders doesn't cause it to load messages. FYI, I just built from source (your master branch), and I noticed your build depends on gobject-introspection, but configure doesn't check for it. Want me to file a bug on that?
Thanks. We'll have to puzzle over your debug logs to try to figure out what's going on. The configure issue is bug 748464.
Ah, yes. That's the same issue. FYI, I was going to check if I see the same behavior in your latest source, but I'm on the VPN and having routing issues. I'll let you know next week if there's any difference.
Ok, I still see the same behavior in your latest master branch (as of 2015-04-28).
I don't see in the debug any indication that the server is notifying Geary of new messages. Geary detects the count changing in the STATUS calls, but since it has the Inbox open it assumes the Inbox connection will be notified and download the messages. We'll need to see a more thorough debug log to trace this problem.
Would '--debug --log-network' get us enough information?
'--debug --log-network' are actually the parameters I used to collect the debug that's attached.
What do we need, then, Jim? A longer session?
*** Bug 752155 has been marked as a duplicate of this bug. ***
If somebody would be willing to explain the layout of the source code to me, and maybe point me where to look, I'd be willing to spend some time debugging this (maybe fix it). I am a developer. I tried poking around in the code and inserted some debug messages, but I quickly got lost in the geary source code.
Hi David, are you still experiencing this issue? If so, it might help adding --log-deserializer so we can get a better understanding of what is going on. This log might be quite large and contain personal information, so feel free to redact email addresses, etc and/or email it to me directly. Also, if you have multiple accounts, please disable all but one that is exhibiting this issue - in 0.12 this can be done by moving the account's config directories out of ~/.config/geary. Thanks!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!