GNOME Bugzilla – Bug 631665
imapx abort
Last modified: 2013-09-14 16:54:00 UTC
Got an ADSL outage, shortly followed by... (evolution:26159): camel-WARNING **: Could not connect to linux.intel.com (port imaps): Connection reset by peer (evolution:26159): camel-CRITICAL **: camel_tcp_stream_connect: assertion `error == NULL || *error == NULL' failed (evolution:26159): camel-WARNING **: Could not connect to linux.intel.com (port imaps): (evolution:26159): camel-CRITICAL **: camel_tcp_stream_connect: assertion `error == NULL || *error == NULL' failed (evolution:26159): camel-WARNING **: Could not connect to linux.intel.com (port imaps): And evolution exited.
I tried to reproduce this with actual git master with no luck. I have a company account accessed through VPN, also using SSL. If I let imapx refresh one folder, and I disconnect VPN during that refreshing, then nothing like this happens, it only timeouts. I suppose dropping VPN is pretty similar to ADSL outage, isn't it? I'm using plain password for authentication, whether it plays any role here. Could you attach backtrace of evolution, to see where it actually crashed, please?
It's probably just a manifestation of bug 631290. Will re-open if it happens again, and obviously try to catch it in gdb. I think abrt might have caught this one but I don't really know how to find its droppings... *** This bug has been marked as a duplicate of bug 631290 ***