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:
Evolution crashed during connectivity changes

Version-Release number of selected component:
evolution-3.8.5-26.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        evolution
crash_function: store_go_online_cb
executable:     /usr/bin/evolution
kernel:         3.10.0-175.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            16189

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 store_go_online_cb at mail-folder-cache.c:1014
 #1 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #2 complete_in_idle_cb_for_thread at gsimpleasyncresult.c:831
 #7 gtk_main at gtkmain.c:1156

Created attachment 945680 [details]
File: backtrace

Created attachment 945681 [details]
File: cgroup

Created attachment 945682 [details]
File: core_backtrace

Created attachment 945683 [details]
File: dso_list

Created attachment 945684 [details]
File: environ

Created attachment 945685 [details]
File: limits

Created attachment 945686 [details]
File: maps

Created attachment 945687 [details]
File: open_fds

Created attachment 945688 [details]
File: proc_pid_status

Created attachment 945689 [details]
File: var_log_messages

Created attachment 945690 [details]
File: binary

Created attachment 945691 [details]
File: sosreport.tar.xz

Thanks for a bug report. This seems to be new, I didn't fins anything similar upstream, but it can be also a coincidence after a different issue, like the:
> (evolution:18963): Gdk-WARNING **: XID collision, trouble ahead
which is shown between messages several times.

What are the account types you've configured, please? That may have certain influence on the reproducibility. You can see it in Edit->Preferences->Mail Accounts, the last column in the list of configured accounts. Also, did you see it in 3.12.11 of evolution-data-server and evolution? There had been done many changes between the 3.8.x and 3.12.x.

imapx, google, caldav, webcal. Anyway, I didn't see this bug for quite some time even in 3.8 so I'm in favour of closing as CURRENTRELEASE.

Okay. Even I'm pretty sure it'll strike back as soon as I'll close this, I'll close this anyway. Thanks.