After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 554593 - Abort/Resume file transfer via SSH when network connection is lost
Abort/Resume file transfer via SSH when network connection is lost
Status: RESOLVED DUPLICATE of bug 124783
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-01 17:04 UTC by Christoph Langner
Modified: 2012-08-20 21:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christoph Langner 2008-10-01 17:04:56 UTC
Since ages it is possible to connect via ssh://<username>@<hostname> to a remote computer and to transmit files inside Nautilus. This works quite good, but only when you've got a stable network connection. My one here is quite shaky... So what happens when I loose my network connection: Nothing...

 * The transfer window still says that i'm receiving data (It shows a estimated end of the transfer and a connection speed), but no data is received.

 * I can hit the "abort"-button, it get's grey, but nothing is aborted. I can't close this windows. I have to kill nautilus to get rid of it.

 * A ssh task prevents Nautilus from re-accessing my SSH Server, i have to kill this process manually with Nautilus. If i don't do this, i can't access my ssh server.

$ ps aux | grep ssh
<username>     22940  0.0  0.2   5328  2372 pts/1    Ss+  18:43   0:00 ssh -oForwardX11 no -oForwardAgent no -oClearAllForwardings yes -oProtocol 2 -oNoHostAuthenticationForLocalhost yes -l y <username> -s <hostname> sftp

What should happen when I transfer files via SSH (and probably other file transfer protocols) and my computer looses it internet connection? 

 * Nautilus should be aware that the connection has been lost. Perhaps we could use the information the network manager is providing.

 * I should be able to abort the whole process. I shouldn't have to kill nautilus and ssh.

 * Resume the download after the connection is reestablished. I should have the option to resume my transfer after i regained network access.
Comment 1 nodiscc 2012-08-18 11:57:40 UTC
Thanks for reporting this, confirmed in Nautilus 3.4.2-1 on Debian.

> * Nautilus should be aware that the connection has been lost. Perhaps we could
> use the information the network manager is providing.
Yes. Maybe the transfer dialog should enter a "waiting for connection" state and inform us that the connection has been dropped, and that it is waiting for it to come back, or for the user to cancel the transfer.

> * I should be able to abort the whole process. I shouldn't have to kill
> nautilus and ssh.
Yes. For now cancelling the transfer apparentely does nothing but graying out the cancel button.

> * Resume the download after the connection is reestablished. I should have the
> option to resume my transfer after i regained network access.
This. Maybe we should open another bug report for a "resume transfer" feature in Nautilus. Actually it can't resume transfers even for local files.

Should we open specific bugs for each of these points? Your input is welcome.
Comment 2 William Jon McCann 2012-08-20 21:55:54 UTC

*** This bug has been marked as a duplicate of bug 124783 ***