Created attachment 912019 [details] backtraces of evolution Description of problem: Evolution downloading new messages too long even if no new messages Demonstration: https://drive.google.com/file/d/0B0nwzlfiB4aQYjFINzRObDZwZms/edit?usp=sharing
$ rpm -qa | grep evolution evolution-data-server-debuginfo-3.12.3-1.fc20.i686 evolution-data-server-3.12.3-1.fc20.i686 evolution-debuginfo-3.12.3-1.fc20.i686 evolution-ews-debuginfo-3.12.3-1.fc20.i686 evolution-3.12.3-1.fc20.i686 evolution-ews-3.12.3-1.fc20.i686 Console out: [mikhail@localhost ~]$ evolution (evolution:2083): evolution-mail-WARNING **: (mail-send-recv.c:1122):receive_update_got_folderinfo: runtime check failed: (info != NULL) (evolution:2083): evolution-mail-WARNING **: receive_update_got_folderinfo: Invalid password with username ‘m_gavrilov’ (goa-error-quark, 0): Code: 2 — Unexpected response from server (evolution:2083): evolution-mail-WARNING **: handle_contact_photo_request: Unable to connect to 'Global Address List': Cannot open book: Invalid password with username ‘m_gavrilov’ (goa-error-quark, 0): Code: 2 — Unexpected response from server (evolution:2083): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed (evolution:2083): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed (evolution:2083): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed (evolution:2083): evolution-mail-WARNING **: handle_contact_photo_request: Unable to connect to 'Global Address List': Cannot open book: Invalid password with username ‘m_gavrilov’ (goa-error-quark, 0): Code: 2 — Unexpected response from server (evolution:2083): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed (evolution:2083): evolution-mail-WARNING **: handle_contact_photo_request: Unable to connect to 'Global Address List': Cannot open book: Invalid password with username ‘m_gavrilov’ (goa-error-quark, 0): Code: 2 — Unexpected response from server (evolution:2083): evolution-mail-WARNING **: Failed to refresh folder 'mikhail.v.gavrilov: [Gmail]/Отправленные': H\x919\xaf@ (evolution:2083): evolution-mail-WARNING **: Failed to refresh folder 'mikhail.v.gavrilov: maria-developers': TLS connection closed unexpectedly
I think the issue is similar as yours bug 1112451, where there the error about incorrect password was not properly propagated into Send/Receive dialog, here the unexpected disconnect form a GMail account caused never-ending message download. The garbage shown on the console at > Failed to refresh folder ... [Gmail]/Отправленные': H\x919\xaf@ suggests some memory misuse too.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.