nautilus stops reacting when sftp connection gets interrupted

[René Walendy]

Steps to reproduce the error:
- connect to LAN
- open a nautilus window
- connect to an sftp server (select directly forget password)
- browse the directory
- disconnect LAN
- connect WLAN (same router)
-> that means network is still connected but the sftp connection is now interrupted
- double click a folder from the sftp server

What should happen:
- nautilus should open the sftp folder, re-connecting to the server, or at least show an error message that the connection got interrupted

What happens instead:
- nautilus does nothing, waiting forever for the server to respond
- all other folders can be accessed
- after closing the last nautilus window nautilus will not start any more until you logout and login again

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu9.3
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 26 21:37:53 2014
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']"
InstallationDate: Installed on 2013-10-10 (320 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: nautilus
UpgradeStatus: Upgraded to trusty on 2014-04-18 (130 days ago)
usr_lib_nautilus:
 deja-dup 30.0-0ubuntu4
 evince 3.10.3-0ubuntu10.1
 file-roller 3.10.2.1-0ubuntu4.1
 nautilus-share 0.7.3-1ubuntu5
 totem 3.10.1-1ubuntu4

[René Walendy (0k53-rene-f830)]

Found a workaround:

1.) open a terminal
2.) run gvfs-mount -u sftp://<insert hostname here>/
3.) gvfs-sftp will crash
4.) all sftp connections are dropped and nautilus will no longer refuse to start
5.) you can now reconnect to your sftp server

[Sebastien Bacher (seb128)]

The bug is years old without activity nor recent similar report, closing as deprecate. You can open a new bug if that's still an issue though