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.el7.1

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

Truncated backtrace:
Thread no. 1 (6 frames)
 #4 g_weak_ref_set at gobject.c:4127
 #5 signal_closure_free at e-cal-client.c:182
 #6 g_source_callback_unref at gmain.c:1545
 #7 g_source_destroy_internal at gmain.c:1204
 #11 g_main_context_iteration at gmain.c:3766
 #12 g_application_run at gapplication.c:1623

Created attachment 902066 [details]
File: backtrace

Created attachment 902067 [details]
File: cgroup

Created attachment 902068 [details]
File: core_backtrace

Created attachment 902069 [details]
File: dso_list

Created attachment 902070 [details]
File: environ

Created attachment 902071 [details]
File: limits

Created attachment 902072 [details]
File: maps

Created attachment 902073 [details]
File: open_fds

Created attachment 902074 [details]
File: proc_pid_status

Created attachment 902075 [details]
File: var_log_messages

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

Corresponding upstream bug report, but with no resolution/fix so far:
https://bugzilla.gnome.org/show_bug.cgi?id=698342

No steps or clues available?

Could you retry with the evolution 3.12.11 and report back, please?

This just happened once. I don't know how to reproduce and I don't see that many crashes in e-a-n.

Thanks for the update. In that case I'm closing this, due to lack of a reproducer.