Version-Release number of selected component: evolution-data-server-3.20.5-5.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory contacts --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx1841x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/1841/2 crash_function: g_wakeup_new executable: /usr/libexec/evolution-calendar-factory-subprocess global_pid: 1907 kernel: 4.8.6-201.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 0 (10 frames) #3 g_wakeup_new at gwakeup.c:161 #4 g_main_context_new at gmain.c:653 #5 g_dbus_connection_send_message_with_reply_sync at gdbusconnection.c:2134 #6 g_dbus_connection_call_sync_internal at gdbusconnection.c:5930 #7 g_dbus_connection_call_with_unix_fd_list_sync at gdbusconnection.c:6276 #8 g_dbus_proxy_call_sync_internal at gdbusproxy.c:2854 #9 g_dbus_proxy_call_sync at gdbusproxy.c:3046 #10 e_dbus_address_book_call_retrieve_properties_sync at e-dbus-address-book.c:1815 #11 book_client_retrieve_properties_sync at e-book-client.c:1018 #12 client_wait_for_connected_thread at e-client.c:1863
Created attachment 1219734 [details] File: backtrace
Created attachment 1219735 [details] File: cgroup
Created attachment 1219736 [details] File: core_backtrace
Created attachment 1219737 [details] File: dso_list
Created attachment 1219738 [details] File: environ
Created attachment 1219739 [details] File: limits
Created attachment 1219740 [details] File: maps
Created attachment 1219741 [details] File: mountinfo
Created attachment 1219742 [details] File: namespaces
Created attachment 1219743 [details] File: open_fds
Created attachment 1219744 [details] File: proc_pid_status
Created attachment 1219745 [details] File: var_log_messages
Thanks for a bug report. I see in the backtrace: > Creating pipes for GWakeup: Too many open files which is also indicated in the open_fds, which shows 1024 opened file descriptors. The problem is that I do not see from the backtrace the circumstances. Are you able to reproduce this anyhow, please?
Milan Crha, hm – I can’t reproduce this. I seem to remember that this crash popped up when I opened GNOME Calendar. I don’t use Evolution itself all that often, and 90 % of the time I use GNOME Calendar as read-only with CalDAV and iCal-file-over-HTTP-subscriptions. Not sure if these details are at all useful.
Thanks for the update. This once crashed in a Birthdays & Anniversaries calendar. Maybe an issue with one of your address books marked for inclusion in this calendar.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.