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.

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

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

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 gtkhtml_editor_freeze at /lib64/libgtkhtml-editor-4.0.so.0
 #1 composer_load_signature_cb at /usr/lib64/evolution/3.8/libcomposer.so
 #2 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #3 mail_signature_combo_box_load_cb at /usr/lib64/evolution/3.8/libeutil.so
 #4 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #5 complete_in_idle_cb_for_thread at gsimpleasyncresult.c:845
 #10 gtk_main at gtkmain.c:1156

Created attachment 899598 [details]
File: backtrace

Created attachment 899599 [details]
File: cgroup

Created attachment 899600 [details]
File: core_backtrace

Created attachment 899601 [details]
File: dso_list

Created attachment 899602 [details]
File: environ

Created attachment 899603 [details]
File: exploitable

Created attachment 899604 [details]
File: limits

Created attachment 899605 [details]
File: maps

Created attachment 899606 [details]
File: open_fds

Created attachment 899607 [details]
File: proc_pid_status

Created attachment 899608 [details]
File: var_log_messages

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

Similar Fedora bug #985527, but no resolution so far. Are there any steps what you did before the crash, please?

(In reply to Milan Crha from comment #14)
> Similar Fedora bug #985527, but no resolution so far. Are there any steps
> what you did before the crash, please?

Nothing particular I would be aware of, but it is a long time. If this seems like nothing interesting, feel free to close it as INSUFFICIENT_DATA.

It's not about "not being interesting", it's about "not being able to reproduce the issue, thus properly investigate it". Please reopen, in case you'll find any steps/data (even the signature itself can play a role, and whether it's set in the account as a default signature or set manually in the composer) for a reproducer.