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.
The problem is an invalid unref in atk, causing crash in at-spi2-atk with invalid g_object_unref() call, on an already freed object. I filled an upstream bug [1] with a fix for it already.
The backtrace from the FAF report is:
Thread 1 (Thread 0x7fb800d11a80 (LWP 25909)):
#0 0x00007fb7f5c864ad in g_type_check_instance_is_fundamentally_a () from /lib64/libgobject-2.0.so.0
#1 0x00007fb7f5c68537 in g_object_unref () from /lib64/libgobject-2.0.so.0
#2 0x00007fb7eaa68b5d in expiry_func () from /lib64/libatk-bridge-2.0.so.0
#3 0x00007fb7f598ceed in g_timeout_dispatch () from /lib64/libglib-2.0.so.0
#4 0x00007fb7f598c4c9 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#5 0x00007fb7f598c818 in g_main_context_iterate.isra.21 () from /lib64/libglib-2.0.so.0
#6 0x00007fb7f598caea in g_main_loop_run () from /lib64/libglib-2.0.so.0
#7 0x00007fb7f74f94b5 in gtk_main () from /lib64/libgtk-3.so.0
#8 0x0000000000403de1 in main ()
https://bugzilla.gnome.org/show_bug.cgi?id=783245
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2100
FOr the record, as found in bug #1717000, the change causes leaks of AtkAObject-s in other than Evolution (like in gnome-shell, which the new bug is filled for).