Red Hat Bugzilla – Bug 1024314
Issues reconnecting when accessing mail via VPN
Last modified: 2015-01-06 18:28:51 EST
In Fedora 19 and all releases prior that I can remember I could suspend my laptop, have the VPN disconnect and at a later point resume, reconnect to the VPN (or if in the office connect to the TFA authed WiFi) and have Evolution reconnect to the mail server and continue as before.
Now if I try to do that it just sits there trying to pull mail. I have to run a "evolution --force-shutdown" and start it up again before it will reconnect with the mail server. All other services behind the VPN work as expected, and evolution, once restarted, does as well. It just use to be that I could hit F-12 and it would pull down and I would continue as I did before.
Thanks for a bug report. Could you provide a backtrace of evolution in that state, please? Once we figure out some more details I'd move this upstream (or we can straight away, if you wish).
I know how to grab a BT of stuff when it's crashing but not sure with evo with it's numerous processes (e-d-s vs evo) when it's running normally. Is there an overview of this?
It's not an exact science, it's sometimes worthless to get backtraces for other evolution processes, all depends on circumstances. I wanted to start with evolution itself, because all the mail is handled there. We can follow base don the backtrace state to other processes, if needed.
By the way, due to sever regressions found in bug #1022750, I reverted one patch from evolution-data-server in Fedora 19. The change is currently in updates testing , maybe it's related to your issue, maybe not.
I have the same issue (I think) in Fedora 20. The version of evolution/evolution-data-server I have is:
If I have evolution open when I connect to my work VPN with openconnect it just spins while trying to get mail.
If I close evolution and reopen, it works fine again.
I think it's some kind of regression in 3.10.x, thus I moved this upstream finally, as . Please see  for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.
*** Bug 1037977 has been marked as a duplicate of this bug. ***
The answer upstream is:
"This should work better in 3.12, where each email account now manages its own
online/offline state with the help of GNetworkMonitor."
How soon can we see 3.12.x in Fedora?
(In reply to David Dreggors from comment #7)
> How soon can we see 3.12.x in Fedora?
3.12 will be part of Fedora 21. Nonetheless, I run that development version and I also see issues on reconnecting, thus the 3.12 (actually 3.11.4) doesn't have it done better yet.
Still not done in evolution-ews-3.12.9-1.fc21.x86_64, just FYI.