Hide Forgot
Version-Release number of selected component: gvfs-1.28.3-1.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-trash --spawner :1.13 /org/gtk/gvfs/exec_spaw/0 crash_function: _g_log_abort executable: /usr/libexec/gvfsd-trash global_pid: 2275 kernel: 4.7.2-201.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:325 #3 g_wakeup_new at gwakeup.c:161 #4 g_main_context_new at gmain.c:653 #5 initable_init at gdbusproxy.c:1936 #6 g_initable_new_valist at ginitable.c:228 #7 g_initable_new at ginitable.c:146 #8 gvfs_dbus_enumerator_proxy_new_sync at gvfsdbus.c:15919 #9 create_enumerator_proxy at gvfsjobenumerate.c:125 #10 send_infos at gvfsjobenumerate.c:158 #11 g_vfs_job_enumerate_done at gvfsjobenumerate.c:250
Created attachment 1200315 [details] File: backtrace
Created attachment 1200316 [details] File: cgroup
Created attachment 1200317 [details] File: core_backtrace
Created attachment 1200318 [details] File: dso_list
Created attachment 1200319 [details] File: environ
Created attachment 1200320 [details] File: limits
Created attachment 1200321 [details] File: maps
Created attachment 1200322 [details] File: mountinfo
Created attachment 1200323 [details] File: namespaces
Created attachment 1200324 [details] File: open_fds
Created attachment 1200325 [details] File: proc_pid_status
Created attachment 1200326 [details] File: var_log_messages
Thanks for your report. It was aborted due to the following error: "Creating pipes for GWakeup: Too many open files" (1024 fds were used as per open_fds). Maybe we leak file descriptors somewhere. Do you remember what did you do when it happened? Are you able to reproduce it?
No, sorry. I just press the appropriate buttons to report the problems when they show up in the bug report tool. Sorry I can't be of more help.
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.