GNOME Bugzilla – Bug 669219
Deadlock in offline/online
Last modified: 2012-02-10 10:22:18 UTC
Evolution 3.3.5 1. clicked on send/receive 2. network went down, evolution showed message about network outage 3. network came back, it was trying to fetch messages and status bar showed that evolution is online can be a duplicate of bug 669108 gdb trace of evolution
+ Trace 229580
Thread 2 (Thread 0xb5e42b70 (LWP 29130))
Thread 1 (Thread 0xb611d890 (LWP 29127))
It's waiting on your server response, inside the Unsubscribe call. If you are really offline, then it'll recover after connection timeouts, then it'll get stuck on Logoff call, if it'll not crash as in bug #669308. I'm not sure if there is anything to be done with this. Maybe the disconnect is not needed to call the Unsubscribe, as the Logoff should close connections to the server anyway, but it'll get stuck on the above-mentioned Logoff too.
As we spoke on IRC, after change from bug #669308, this is stuck in the Logoff() (see the below backtrace). You also mentioned that it didn't recover after 5 minutes of waiting, which seems like there is either no default timeout limit on tevent or it's too high. We may cope with this within bug #608327, as it's closely related.
+ Trace 229638
Thread 27 (Thread 0xa699cb70 (LWP 7471))
*** This bug has been marked as a duplicate of bug 608327 ***