RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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' (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:

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.

I use primarily Fedora version of Evolution for some time already so I'm unlikely to hit this again...