Version-Release number of selected component: gvfs-1.26.2-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-dav --spawner :1.9 /org/gtk/gvfs/exec_spaw/11 crash_function: magazine_chain_pop_head executable: /usr/libexec/gvfsd-dav global_pid: 8138 kernel: 4.2.8-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:539 #1 thread_memory_magazine1_alloc at gslice.c:842 #2 g_slice_alloc at gslice.c:998 #3 g_variant_alloc at gvariant-core.c:476 #4 g_variant_new_from_bytes at gvariant-core.c:512 #5 g_variant_new_from_trusted at gvariant.c:295 #6 g_variant_new_object_path at gvariant.c:1330 #7 set_object_path_header at gdbusmessage.c:2843 #8 g_dbus_message_set_path at gdbusmessage.c:3002 #9 g_dbus_message_new_method_call at gdbusmessage.c:612 Potential duplicate: bug 1036184
Created attachment 1113009 [details] File: backtrace
Created attachment 1113010 [details] File: cgroup
Created attachment 1113011 [details] File: core_backtrace
Created attachment 1113012 [details] File: dso_list
Created attachment 1113013 [details] File: environ
Created attachment 1113014 [details] File: exploitable
Created attachment 1113015 [details] File: limits
Created attachment 1113016 [details] File: maps
Created attachment 1113017 [details] File: mountinfo
Created attachment 1113018 [details] File: namespaces
Created attachment 1113019 [details] File: open_fds
Created attachment 1113020 [details] File: proc_pid_status
Created attachment 1113021 [details] File: var_log_messages
Another user experienced a similar problem: Tried cancelling connecting to a davs:// (webdav) server. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-dav --spawner :1.14 /org/gtk/gvfs/exec_spaw/14 crash_function: magazine_chain_pop_head executable: /usr/libexec/gvfsd-dav global_pid: 7974 kernel: 4.3.3-300.fc23.x86_64 package: gvfs-1.26.2-1.fc23 reason: gvfsd-dav killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.