After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772948 - On startup, Geary refetches(?) all mails
On startup, Geary refetches(?) all mails
Status: RESOLVED DUPLICATE of bug 713530
Product: geary
Classification: Other
Component: engine
master
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-10-14 16:44 UTC by Gautier Pelloux-Prayer
Modified: 2016-10-15 01:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gautier Pelloux-Prayer 2016-10-14 16:44:57 UTC
Not sure if the title is exact, but everytime I open Geary,  it starts fetching mails in background for more than 2 minutes and I can see lots of:

> 18:42:09 0,212072 imap-engine-account-synchronizer.vala:409: Background sync'ing Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true) to 2006-12-27T16:14:35+0000
> 18:42:09 0,000825 imap-engine-minimal-folder.vala:1508: Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true): find_earliest_email_async: (since 27-Dec-2006 uid 1:8)
> 18:42:11 1,221296 imap-engine-minimal-folder.vala:1529: Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true): find_earliest_email_async: found (null)
> 18:42:11 0,218056 imap-engine-account-synchronizer.vala:409: Background sync'ing Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true) to 2006-11-27T16:14:35+0000
> 18:42:11 0,001251 imap-engine-minimal-folder.vala:1508: Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true): find_earliest_email_async: (since 27-Nov-2006 uid 1:8)
> 18:42:11 0,200214 imap-engine-minimal-folder.vala:1529: Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true): find_earliest_email_async: found (null)
> 18:42:11 0,228709 imap-engine-account-synchronizer.vala:409: Background sync'ing Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true) to 2006-10-27T16:14:35+0000
> 18:42:11 0,002125 imap-engine-minimal-folder.vala:1508: Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true): find_earliest_email_async: (since 27-Oct-2006 uid 1:8)
> 18:42:11 0,230365 imap-engine-minimal-folder.vala:1529: Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true): find_earliest_email_async: found (null)
> 18:42:12 0,227013 imap-engine-account-synchronizer.vala:409: Background sync'ing Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true) to 2006-09-27T16:14:35+0000
> 18:42:12 0,001563 imap-engine-minimal-folder.vala:1508: Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true): find_earliest_email_async: (since 27-Sep-2006 uid 1:8)
> 18:42:12 0,201817 imap-engine-minimal-folder.vala:1529: Gmail:gautier.pelloux@gmail.com:[Gmail]>Tous les messages (open_count=1 remote_opened=true): find_earliest_email_async: found (null)


It happens at every startup, no matter what. I would expect Geary to do almost nothing by default (eg if its already up-to-date), so I believe there is a bug…

This happens both for my gmail account and my custom account.
Comment 1 Michael Gratton 2016-10-15 01:48:22 UTC
This is the background synchroniser, it's not re-fetching all mail, just looking for changed messages. Bug 714637 was the original ticket covering it, but it also gets used to look for new folders, and things like finding newly-sent mail in Sent folders.

I've never been too sure why this approach is necessary, but it might have something to do with how IMAP IDLE works. But I agree it would be good to look for alternatives.

Since this is basically the same issue Bug 713530, I'm going mark it as a duplicate of that.

*** This bug has been marked as a duplicate of bug 713530 ***