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 429065 [details]
Stack trace from the crash

Description of problem:
I'm trying to have evolution contact an Exchange 5.5 server using MAPI, in order to manage my meeting invitations.  However, after having configured server and user name and when pressing "Authenticate", evolution crashes.

Version-Release number of selected component (if applicable):
Many could be involved, but these are the more obviously relevant ones:
evolution-mapi-0.28.2-1.el6.x86_64
evolution-data-server-2.28.2-3.el6.x86_64
evolution-2.28.2-3.el6.x86_64


How reproducible:
Every time

Steps to Reproduce:
1. Configure an MAPI account in evolution
2. Click "authenticate"
  
Actual results:
Crash

Additional info:
I enclose the backtrace.  The output on the console after clicking is

Create profile with goran.uddeborg corp entframail1.corp.gds.jeppesen.com
libexchangemapi-Message: exchange-mapi-connection.c:3029: exchange_mapi_create_profile: lock(connect_lock)
Logging into the server... Abort (core dumped)

I upgraded to "beta 2 refresh", and the behaviour has changed.  Now I can authenticate, and some of my appointments are shown.  Not all, and if I try to add a new everything hangs.  So it's not quite working yet, but I can't reproduce this particular problem any more.

Göran,
could you please open a new bug for what you are seeing so we can close this authentication crasher and continue solving the UI freeze?

thanks,
Vladimir

I actually did that after writing comment 7, but forgot to add another comment here.

Bug 621941 and bug 621943 describe the problems I see with the latest beta.

according to comment 5 and comment 7 this fix was verified
-> VERIFIED

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.