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 768436 [details]
evo bt

Description of problem:
evolution copies calendar synchronously

Version-Release number of selected component (if applicable):
evolution-2.32.3-9.el6.x86_64
evolution-data-server-2.32.3-7.el6.x86_64

How reproducible:
didn't try to reproduce

Steps to Reproduce:
1. have a local calendar with some data and empty caldav calendar
2. right-click the local calendar, select "copy", select caldav calendar, confirm
3.

Actual results:
evo UI doesn't respond till the copying is over

Expected results:
evo performs copying in the background with progress indication in status bar

Additional info:

Created attachment 768437 [details]
e-c-f bt

Created attachment 768438 [details]
e-a-f bt

That's true, many calendar operations are done synchronously, on the main thread. It's to be done in upstream first (and is in my long term to-do). If you want, then I can do this particular function first and do the rest in upstream only, when the time comes; otherwise I'd just close this.

Let's do not do this, and wait for the upstream, when it's fixed. Only note that a backport from an upstream to rhel6.5 is undoable, due to move between 2.32.3 and 3.9.4 (current git master).