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 315064 - can't cancel stalled remote transfer
can't cancel stalled remote transfer
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.15.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-01 20:23 UTC by Sebastien Bacher
Modified: 2008-10-11 21:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Sebastien Bacher 2005-09-01 20:23:50 UTC 
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=14469 

"* go to remoteProtocol://user@host/... with nautilus
* pick a somewhat large file and drag it to a local folder
* unplug your network cable/ifdown your interface to simulate a network problem
* the transfer is stalled, try to cancel it, you can't, you have to kill nautilus

tested with sftp and ftp, in nautilus 2.10 (hoary PPC) and 2.11.9x (up to date
breezy i386 and AMD64)
gnomevfs-copy IS interruptible in the same situation"
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2006-04-24 15:48:46 UTC 
I can confirm this. It's very annoying. (I'm using Nautilus 2.14.1 from ubuntu dapper).
Comment 2 Saulius Menkevičius 2006-04-24 17:02:15 UTC 
Nautilus 2.14.1/Ubuntu/x86 (file transfer via ftp, too).
Comment 3 Sebastien Bacher 2006-07-31 10:21:50 UTC 
still happening with GNOME 2.15.90, updating settings according to that
Comment 4 Joachim Noreiko 2007-03-23 12:09:40 UTC 
Actually, I can't cancel a remote transfer that's progressing normally.

Separate bug, or a wider scope on this one?
Comment 5 A. Walton 2008-05-18 16:19:24 UTC 
Thanks for reporting this. Is anyone still seeing this issue with Nautilus 2.22? The entire virtual file system layer was replaced, and this issue may have been resolved.
Comment 6 André Klapper 2008-10-11 21:27:25 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!