Description of problem: I changed my wifi connection to wired connection, while having a remote directory opened in Nautilus over SSH. Version-Release number of selected component: gvfs-1.18.3-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-sftp --spawner :1.6 /org/gtk/gvfs/exec_spaw/2 crash_function: _g_log_abort executable: /usr/libexec/gvfsd-sftp kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #2 _g_log_abort at gmessages.c:255 #5 g_vfs_daemon_finalize at gvfsdaemon.c:149 #7 daemon_main at daemon-main.c:407
Created attachment 844719 [details] File: backtrace
Created attachment 844720 [details] File: cgroup
Created attachment 844721 [details] File: core_backtrace
Created attachment 844722 [details] File: dso_list
Created attachment 844723 [details] File: environ
Created attachment 844724 [details] File: limits
Created attachment 844725 [details] File: maps
Created attachment 844726 [details] File: open_fds
Created attachment 844727 [details] File: proc_pid_status
Created attachment 844728 [details] File: var_log_messages
Created attachment 878170 [details] core_backtrace In caja (mate-file-manager), I clicked the eject button for a remote filesystem that was accessed via sftp.
I tried to access an 'sftp://' filesystem. The remote server had been rebooted since the filesystem was mounted. After gvfs crashed, so did Nautilus: [[bugzilla:1029670]]
Another incident - this time while mate-file-manager was originally connected to a remote sftp server while I was connected to a remote network via a VPN. After I had left everything for a while the VPN connection timed out, as did the sftp connection. I then when to reconnect, not realizing that the VPN was down. With the VPN down, the remote server rejected the connection. This was when the crash occurred.
Another incident - I believe this time the previous connection to a remote sftp server had timed out. I clicked the "eject" button in the pane on the left.
*** Bug 1114272 has been marked as a duplicate of this bug. ***
Another incident - After not doing anything for a while, I came back to the window and hit F5; in the middle of that operation I clicked on the "stop" button. ABRT popped up.
The original backtrace and the one in comment 11 should be fixed by upstream commit 9f2651129d86c4d926e7e186813922d2ed5d2e23. See https://bugzilla.gnome.org/show_bug.cgi?id=710986