Version-Release number of selected component: gvfs-1.36.2-2.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-network --spawner :1.20 /org/gtk/gvfs/exec_spaw/2 crash_function: g_wakeup_new executable: /usr/libexec/gvfsd-network journald_cursor: s=630d7ba299274472a27f70f8bad4196a;i=e32eb;b=d06ae07653e646cfa095b5371a8e549f;m=107f93250;t=5748f7da19428;x=8afb585905439cac kernel: 4.17.18-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 g_wakeup_new at gwakeup.c:161 #5 g_main_context_new at gmain.c:656 #6 initable_init at gdbusproxy.c:1939 #7 g_initable_new_valist at ginitable.c:248 #8 g_initable_new at ginitable.c:162 #9 gvfs_dbus_enumerator_proxy_new_sync at gvfsdbus.c:16117 #10 create_enumerator_proxy at gvfsjobenumerate.c:125 #11 send_infos at gvfsjobenumerate.c:158 #12 g_vfs_job_enumerate_done at gvfsjobenumerate.c:250 #13 try_enumerate at gvfsbackendnetwork.c:761 Potential duplicate: bug 1558086
Created attachment 1479418 [details] File: backtrace
Created attachment 1479419 [details] File: cgroup
Created attachment 1479420 [details] File: core_backtrace
Created attachment 1479421 [details] File: cpuinfo
Created attachment 1479422 [details] File: dso_list
Created attachment 1479423 [details] File: environ
Created attachment 1479424 [details] File: limits
Created attachment 1479425 [details] File: maps
Created attachment 1479426 [details] File: mountinfo
Created attachment 1479427 [details] File: open_fds
Created attachment 1479428 [details] File: proc_pid_status
Created attachment 1479429 [details] File: var_log_messages
Just a summary of yesterday debugging session with Christian: This is because of "Creating pipes for GWakeup: Too many open files". For some reason, too many sockets were opened, see attachment 1479427 [details] and reached the limits, see attachment 1479424 [details]. As per the FAF, it happens also with other daemons sometimes. It goes about "unix:abstract=/dbus-vfs-daemon/socket-*" sockets (see gvfsdaemon.c) as per "lsof" output. It is not possible to find a peer for many of them, but it is not clear why. Simple tests show that the sockets are closed properly after client termination. Any ideas?
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.