Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1172143 +++
The problem is that the evolution-ews is creating its own instance of an ESourceRegistry, at the place shown in the below backtrace. This ESourceRegistry has scheduled the source_registry_source_notify_enabled_idle_cb() while the 'registry' object is disposing, which later leads to the crash when using already freed data in the callback. I'm checking how to fix this in the most sane way.
#6 0x00007ffff52d62f3 in e_source_registry_new_sync (cancellable=0x0, error=0x0) at e-source-registry.c:1677
#7 0x00007fffd27c529b in ews_store_maybe_update_sent_and_drafts (ews_store=0x13ebf30, ews_folders=0xc1d2b0 = {...}) at camel-ews-store.c:904
#8 0x00007fffd27c5d16 in ews_authenticate_sync (service=0x13ebf30, mechanism=0x7fff98008190 "NTLM", cancellable=0x1488c90, error=0x7fffad325920) at camel-ews-store.c:1124
#9 0x00007ffff489476e in camel_service_authenticate_sync (service=0x13ebf30, mechanism=0x7fff98008190 "NTLM", cancellable=0x1488c90, error=0x7fffad325920) at camel-service.c:2017
#10 0x00007fffd1ef1ab0 in mail_authenticator_try_password_sync (auth=0x14a7540, password=0x7fffc8404e80, cancellable=0x1488c90, error=0x7fffad325920) at e-mail-authenticator.c:165
#11 0x00007ffff52c750f in e_source_authenticator_try_password_sync (auth=0x14a7540, password=0x7fffc8404e80, cancellable=0x1488c90, error=0x7fffad325920) at e-source-authenticator.c:418
#12 0x00007ffff52d6747 in source_registry_authenticate_authenticate_cb (dbus_auth=0x13d5960,
The fix is already included in the rebased 3.12.11, thus I mark this as a duplicate of it.
*** This bug has been marked as a duplicate of bug 1174417 ***