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-data-server-3.8.5-21.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: id_hash
executable:     /usr/libexec/evolution-calendar-factory
kernel:         3.10.0-86.el7.x86_64
runlevel:       unknown
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 id_hash at e-data-cal-view.c:138
 #1 g_hash_table_lookup_node at ghash.c:365
 #2 g_hash_table_insert_internal at ghash.c:1153
 #3 notify_add_component at e-data-cal-view.c:756
 #4 e_data_cal_view_notify_components_added at e-data-cal-view.c:1206
 #5 e_cal_backend_http_start_view at e-cal-backend-http.c:1183
 #6 calview_start_thread at e-data-cal-view.c:174
 #7 g_thread_proxy at gthread.c:798

Created attachment 862824 [details]
File: backtrace

Created attachment 862825 [details]
File: cgroup

Created attachment 862826 [details]
File: core_backtrace

Created attachment 862827 [details]
File: dso_list

Created attachment 862828 [details]
File: limits

Created attachment 862829 [details]
File: maps

Created attachment 862830 [details]
File: open_fds

Created attachment 862831 [details]
File: proc_pid_status

Created attachment 862832 [details]
File: var_log_messages

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

Similar upstream bug report [1], not yet fixed upstream, unfortunately.

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

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

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