Bug 1288046 - Evolution gets some stuck "... (cancelling)" tasks after connectivity breaks (e.g. laptop undock) [NEEDINFO]
Evolution gets some stuck "... (cancelling)" tasks after connectivity breaks ...
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution (Show other bugs)
7.2
Unspecified Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Milan Crha
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-03 06:23 EST by David Jaša
Modified: 2017-03-09 13:00 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
mcrha: needinfo? (djasa)


Attachments (Terms of Use)
backtrace for "Reconnecting to '<account_name>' (cancelling)" (46.19 KB, text/plain)
2015-12-03 06:23 EST, David Jaša
no flags Details

  None (edit)
Description David Jaša 2015-12-03 06:23:51 EST
Created attachment 1101782 [details]
backtrace for "Reconnecting to '<account_name>' (cancelling)"

Description of problem:
When using evolution with hard connection breaks (e.g. pull laptop out of dock, suspend, resume elsewhere or at the same location after a couple of hours), I'm getting some stuck network operations, some still active, some "cancelling". The attached backtrace is an example of evo in such a state, the particular message is: "Reconnecting to 'acount_name@example.org' (cancelling)".

When in such a state, evo can't be cleanly shut down, it has to be killed with 9. Stop button (per task or global) has no effect either. Otherwise, the program works mostly normally, I noticed some IMAP sync issues but I can't tell for sure that they are caused by this bug.


Version-Release number of selected component (if applicable):
evolution-3.12.11-15.el7.x86_64
evolution-data-server-3.12.11-24.el7.x86_64

How reproducible:
frequent

Steps to Reproduce:
1. use Evo on location-changing over some time, do hard connectivity breaks
2.
3.

Actual results:
Evo develops 'cancelling' tasks that are cancelling forever

Expected results:
Evo handles sudden connectivity breaks gracefully

Additional info:
Comment 1 Milan Crha 2015-12-03 12:41:59 EST
Thanks for a bug report. The backtrace shows just that, the IMAPx account is connecting to the server. The thing is that there is missing another thread, which is supposed to do the actual connection. Either it didn't start yet, or the connect failed in some way (could be cancelled) and it didn't tell its initiator about it.

Note You need to log in before you can comment on or make changes to this bug.