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 925717 [details]
backtrace

Description of problem:
Evolution freeze when restoring backup created on rhel5. The freeze happens in Migrating ... dialog during Migrating Folders

Version-Release number of selected component (if applicable):
evolution-2.32.3-33.el6
evolution-data-server-2.32.3-20.el6

How reproducible:
100%

Steps to Reproduce:
1. Restore backup created on rhel5


Actual results:
Evolution freeze

Expected results:
Migration is successful

Additional info:
Could be related or even a dupe of bz#1126916.

(In reply to Jiri Koten from comment #0)
> Additional info:
> Could be related or even a dupe of bz#1126916.

I don't think this one's related.  The backtrace suggests a deadlocked mutex in the migration code.  But that code is ancient and the migration to SQLite was always problematic.  I've long forgotten the details.

Hrm, this might be after a fix for bug #1040178.

Created attachment 930985 [details]
eds patch

for evolution-data-server;

CamelDB did not support nested transactions, while the database migration uses it. I added support for nested transactions in this patch, which fixes the deadlock. This is applicable to current upstream version as well.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1418.html