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 711698 - On network error (common on suspend), folders disappear -- deleting caches and removing search folder configuration
On network error (common on suspend), folders disappear -- deleting caches an...
Status: RESOLVED DUPLICATE of bug 704513
Product: evolution
Classification: Applications
Component: Mailer
3.8.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-11-08 16:33 UTC by Benjamin Kahn
Modified: 2013-11-08 17:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Benjamin Kahn 2013-11-08 16:33:42 UTC
On receiving a networking error, Evolution 3.8.x removes any folders it was in the process of checking. This means that folder caches are cleared and search folder configurations are edited.

mbarnes believes the commit which caused the problem is:
https://git.gnome.org/browse/evolution-data-server/commit/?id=dacf16165d22e08c1f758144ec5e9f4d8c6da0d0

To reproduce:

 * Configure an IMAP account
 * Add a search folder with the INBOX to that IMAP account in the search folder
 * Cause a network error (suspend for 10 minutes and resume, disconnect the network cable, etc)
 * Reconnect the network or resume the laptop

What should happen:

 * Evolution should detect the network error and attempt to reconnect without changing any configuration

What actually happens:

 * Evolution receives a network error, removes the open folders from the display, clears the caches, and removes the folders from the search folder
 * Later, the folders may reappear in the UI, but the configuration will not be restored, and the caches will need to be rebuilt.
Comment 1 Matthew Barnes 2013-11-08 17:12:27 UTC
As I have repeatedly said, this is already fixed in 3.10.

*** This bug has been marked as a duplicate of bug 704513 ***
Comment 2 Benjamin Kahn 2013-11-08 17:19:47 UTC
Yes. You've said that. However, 3.8.x is widely deployed with no hope for updates. (For example Fedora 19.)