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 703975 - Offline network management / IMAP (with IMAPx / IMAP+) caching broken
Offline network management / IMAP (with IMAPx / IMAP+) caching broken
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.8.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[imapx]
Depends on:
Blocks:
 
 
Reported: 2013-07-10 23:36 UTC by Jean-François Fortin Tam
Modified: 2013-07-24 10:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot (137.73 KB, image/png)
2013-07-10 23:36 UTC, Jean-François Fortin Tam
Details

Description Jean-François Fortin Tam 2013-07-10 23:36:35 UTC
Created attachment 248902 [details]
screenshot

Hi there,
Running Evolution 3.8.3 from Fedora 19 64-bit, I am faced with broken network management. I'm not sure if it's something that changed in networkmanager that broke Evo, or something wrong with the caching system, or something broken in the IMAP+ backend...

Typically I leave Evolution open all day, on a laptop connected to a wired network. Then, I suspend the laptop and unsuspend it once I am in public transit (bus/plane/submarine/whatever) without network access.

Now, I'm faced with evolution hiding all my messages, replacing them with "Generating message list..." on the blank background. Nothing in the statusbar. One or two infobars shown at the top, one of which is the yellow "network temporary down, don't panic" one and the other is a new "oops I could not reach that server" error infobar, which is probably the core of the bug. See attached screenshot.

My folders are set to make their contents available offline (verified by right-clicking on my inbox folder and checking its properties). For good measure, I did an evolution --force-shutdown, cleared ~/.cache/evolution and tried again after re-downloading/caching everything; problem still occurs. I have a nice 1 gigabyte cache folder that gets ignored completely :(


Dead-easy way to reproduce: start Evolution 3.8 while your wifi and networking is turned off. Notice that Evolution doesn't realize that the network is unavailable on startup (no yellow infobar, and the "connected" icon is shown on the lower-left corner of Evolution). Try to access your IMAP inbox: ಠ╭╮ಠ



This kind of usecase would be a really really really great candidate for a test suite (if that's not already the case) - the whole point of using IMAP and mail clients instead of web-based thingies is to be able to access your data offline... and it is really not the first time that network management support in Evolution breaks like that :(

Cheers, and let me know if you need additional info.
Comment 1 Milan Crha 2013-07-19 13:05:34 UTC
Thanks for a bug report.

(In reply to comment #0)
> Now, I'm faced with evolution hiding all my messages, replacing them with
> "Generating message list..." on the blank background. Nothing in the statusbar.

This one was fixed recently as commit for 3.8.4+:
https://git.gnome.org/browse/evolution-data-server/commit/?h=gnome-3-8&id=c5fab9b41b3a0c18b54ff8eae3c664a16084912a

> Dead-easy way to reproduce: start Evolution 3.8 while your wifi and networking
> is turned off. Notice that Evolution doesn't realize that the network is
> unavailable on startup

This is bug #700414 - long story short, do not have "Ignore" on IPv6 in Network Manager, but some "Automatic" or such, thus it's not reported to GNetworkMonitor as available.
Comment 2 Jean-François Fortin Tam 2013-07-24 01:20:04 UTC
Whew! Thank you Milan. Making sure I'm understanding you properly: should I expect the whole behavior described here to be fixed without user intervention in 3.8.4, or is the "allow IPv6 in NM's properties" workaround still going to be needed?
Comment 3 Jean-François Fortin Tam 2013-07-24 01:22:43 UTC
Hmm, FWIW I checked in my network settings just now, and none of my connections had IPv6 disabled/ignored, all were set to Automatic (including the wired network device and the two wifi APs I connected to previously)...
Comment 4 Milan Crha 2013-07-24 10:55:42 UTC
Only part of the issue was fixed, the one with IPv6 was not fixed yet. If you see the issue even with Automatic IPv6, then you might face something else, from what I did.