Version-Release number of selected component: gvfs-smb-1.21.90-1.fc22 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-smb --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 crash_function: smbc_getFunctionStat executable: /usr/libexec/gvfsd-smb kernel: 3.17.0-0.rc1.git0.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 smbc_getFunctionStat at /lib64/libsmbclient.so.0 #1 do_query_info #2 g_vfs_job_run at /usr/lib64/gvfs/libgvfsdaemon.so #4 g_thread_proxy at gthread.c:764
Created attachment 930016 [details] File: backtrace
Created attachment 930017 [details] File: cgroup
Created attachment 930018 [details] File: core_backtrace
Created attachment 930019 [details] File: dso_list
Created attachment 930020 [details] File: environ
Created attachment 930021 [details] File: exploitable
Created attachment 930022 [details] File: limits
Created attachment 930023 [details] File: maps
Created attachment 930024 [details] File: open_fds
Created attachment 930025 [details] File: proc_pid_status
Created attachment 930026 [details] File: var_log_messages
This bug should be already fixed in gvfs 1.23.1 by upstream: https://bugzilla.gnome.org/show_bug.cgi?id=710986