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.
Description of problem:
I left my workstation and when I came back evolution was gone.
Version-Release number of selected component:
evolution-3.12.11-22.el7
Additional info:
reporter: libreport-2.1.11.1
backtrace_rating: 4
cmdline: evolution
crash_function: g_type_check_instance_cast
executable: /usr/bin/evolution
global_pid: 10842
kernel: 3.10.0-514.el7.x86_64
pkg_fingerprint: 199E 2F91 FD43 1D51
pkg_vendor: Red Hat, Inc.
reproducible: Not sure how to reproduce the problem
runlevel: N 5
type: CCpp
uid: 3335255
Truncated backtrace:
Thread no. 1 (9 frames)
#0 g_type_check_instance_cast at /lib64/libgobject-2.0.so.0
#1 e_soup_auth_negotiate_message_finished at /usr/lib64/evolution-data-server/libeews-1.2.so.0
#2 _g_closure_invoke_va at /lib64/libgobject-2.0.so.0
#5 soup_session_process_queue_item at /lib64/libsoup-2.4.so.1
#6 async_run_queue at /lib64/libsoup-2.4.so.1
#7 idle_run_queue at /lib64/libsoup-2.4.so.1
#9 g_main_context_iterate.isra.24 at /lib64/libglib-2.0.so.0
#11 e_ews_soup_thread at /usr/lib64/evolution-data-server/libeews-1.2.so.0
#12 g_thread_proxy at /lib64/libglib-2.0.so.0
Thanks for a bug report. I suppose you use 'Kerberos' (GSSAPI) to login to your Exchange account using evolution-ews. I see that var_log_messages has quite some runtime warnings, some of them clearly from this part.
An upstream bug report [1] had some follow-up changes which didn't make it into the 3.12.x, and reading the bug report it's also unsure from the bug report which commits were related.
I would retest this with RHEL 7.4, where the evolution-ews (together with the evolution & co.) will be updated.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=732850