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.

Version-Release number of selected component:
evolution-3.12.8-1.el7

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

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 magazine_chain_pop_head at gslice.c:539
 #1 private_thread_memory_cleanup at gslice.c:784
 #2 __nptl_deallocate_tsd at pthread_create.c:156

Created attachment 1018055 [details]
File: backtrace

Created attachment 1018056 [details]
File: cgroup

Created attachment 1018057 [details]
File: core_backtrace

Created attachment 1018058 [details]
File: dso_list

Created attachment 1018059 [details]
File: environ

Created attachment 1018060 [details]
File: limits

Created attachment 1018061 [details]
File: maps

Created attachment 1018062 [details]
File: open_fds

Created attachment 1018063 [details]
File: proc_pid_status

Created attachment 1018064 [details]
File: var_log_messages

Thanks for a bug report. The backtrace itself is useless, but the var_log_messages suggests that the crash happened due to [1]. That is fixed in evolution 3.12.9+, thus will be part of RHEL7 once it is rebased to 3.12.11.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=734530

*** This bug has been marked as a duplicate of bug 1174415 ***