The upstream bug is very unlikely to get fixed at all now that the backend of nautilus is switching from gnome-vfs to gio/gvfs: whatever the current status, isn't it better to close this bug as wontfix ?
I have juste tested on hardy with the new nautilus and sftp:
* I can cancel a "live" network copy
* A copy continues when the network comes back
* If I unplug the network and then try to cancel the transfer, it does nothing but grey out the cancel button. It will finish to cancel it a while after I plug back the network.
* I have tried to wait 5 minutes for the transfer to timeout in absence of network, it doesn't, and doesn't allow me to cancel it either
So the new situation is a bit better than the previous one, but the problem is still present IMHO.
The upstream bug is very unlikely to get fixed at all now that the backend of nautilus is switching from gnome-vfs to gio/gvfs: whatever the current status, isn't it better to close this bug as wontfix ?
I have juste tested on hardy with the new nautilus and sftp:
* I can cancel a "live" network copy
* A copy continues when the network comes back
* If I unplug the network and then try to cancel the transfer, it does nothing but grey out the cancel button. It will finish to cancel it a while after I plug back the network.
* I have tried to wait 5 minutes for the transfer to timeout in absence of network, it doesn't, and doesn't allow me to cancel it either
So the new situation is a bit better than the previous one, but the problem is still present IMHO.