GNOME Bugzilla – Bug 758152
Network connection not detected on resume from suspend
Last modified: 2017-02-24 00:41:18 UTC
Created attachment 315646 [details] screenshot As the attached screenshot shows, Evolution 3.18.1 fails to detect the presence of a working wired ethernet connection upon resume from suspend. Note that on this computer I have two wired ethernet ports (enp0s25 and enp2s0), if that changes anything. When this happens, there is no way for Evolution to realize the connection is up except to quit the Evolution application and launch it anew. I think I've sometimes seen it fail to detect the connected wifi too, but I'm not totally sure on that front.
Thanks for a bug report. Evolution relies on the GNetworkMonitor with connection detection. It prints on console when it is about to update the connection state in both directions, from offline to online and from online to offline. I see on that mine: evolution-shell-Message: Network disconnected. Forced offline. evolution-shell-Message: Connection established. Going online. I see it there twice. it worked flawlessly the first time, but the second time the evolution got stuck in "going offline" a bit longer, during which "going online" happened, but it was not powerful enough, thus the evolution was left in the offline state anyway, like for you (the unplagged network in the left-bottom corner of your screen shot). Thus yes, I can confirm this with the current git master.
The problem was that the 'Going online' could be received when the evolution was still preparing the offline state, which broke the whole logic, because the shell was in a state of being online, which wasn't correct. Created commit 1c53280 in evo master (3.19.3+) Created commit db8f380 in evo gnome-3-18 (3.18.3+)
*** Bug 750963 has been marked as a duplicate of this bug. ***
*** Bug 758673 has been marked as a duplicate of this bug. ***