GNOME Bugzilla – Bug 624118
FTP copy timeouts, cannot resume, cannot set timeout limit higher
Last modified: 2018-09-21 17:05:37 UTC
For some servers it timeouts while copying files on FTP connection. If it timeouts I have options for stopping the copy or skipping the file. I really don't want to skip the file but want to force copying. I would appreciate a "try again" button. It would help if I could raise the timeout limit too. I don't know why it timeouts. If you need any info about the technical environment for solve my problem, please let me know and tell me how to retrieve it. Thanks!
There is a thread deals with the same problem: http://art.ubuntuforums.org/showthread.php?t=1351032 And I found a hacking solution, but it would be much nicer not to have to run any python script for keepalive. http://ubuntuforums.org/showthread.php?t=1010463
SMB connections also seem to time out (copy failed because "filesystem not mounted"). Selecting skip in the file dialog resumes the copy, but I have to track the skipped file. Why can we not add a "retry" button to this dialog?
Confirming this for ftp, it's making it impossible to copy to my local ftp server (xbmc on xbox), as it times out after about 18mb (of 140). Ideally it would try and reconnect, as I can do this in nautilus and see the files, but have no way to copy all the files I need. Confirmed on nautilus 3.2.1 on ubuntu 11.04. I'm pretty sure I didn't have this problem pre the gvfs transition, which is the last time I tried copying a similar directory to the same place from nautilus.
Can anyone describe the server used and any settings used (e.g. timeouts)? For debug logging, please run the following in a terminal: pkill gvfs; GVFS_DEBUG=all `find /usr/lib* -name 'gvfsd'` &> ~/log.txt Then mount the ftp share, reproduce the problem, and then upload log.txt in your home directory so we can see a log of what is happening.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/154.