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 526010 [details]
backtrace

Description of problem:

evolution was killed by signal 11 (SIGSEGV) in function icon_list_from_theme
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)

Version-Release number of selected component (if applicable):

release: Red Hat Enterprise Linux Workstation release 6.1 (Santiago)
architecture: x86_64
package: evolution-2.28.3-24.el6

How reproducible:
randomly 

Steps to Reproduce:
1.
2.
3.
  
Actual results:
evolution crashed 

Expected results:
evolution should not crash
Additional info:

Thanks for a bug report. I'm marking this as a duplicate of one older, but to be honest there is no exact fix upstream either, see bug [1]. On the other hand, it seems to be fixed with later releases (either evolution or gtk+), because there are no other duplicates than from 2.28.

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

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