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 577160 - gvfs ftp backend appears to not wait for ftpd return code on STOR
gvfs ftp backend appears to not wait for ftpd return code on STOR
Status: RESOLVED DUPLICATE of bug 574968
Product: gvfs
Classification: Core
Component: ftp backend
1.2.x
Other All
: Normal major
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2009-03-29 04:27 UTC by Chris
Modified: 2009-03-29 04:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
log from gvfsd (48.58 KB, text/plain)
2009-03-29 04:29 UTC, Chris 		Details

Description Chris 2009-03-29 04:27:43 UTC 
Please describe the problem:
When attempting to get OpenOffice.org to save a file to gvfs fuse using ftp backend I noticed it was failing. I debugged gvfsd and it appears the problem is that gvfs ftp backend does not actually wait for the return code from the ftpd server for the STOR command and does a list before it returns seeing the size of the file is still 0.

Steps to reproduce:
1. attempt to save a file to gvfs fuse using ftp backend
2. notice it fails to save
3. look in the gvfsd log file

Actual results:
it fails to save

Expected results:
it should work

Does this happen every time?
yes

Other information:
Ubuntu 9.04 Beta - gvfs 1.2.0-0ubuntu1
Comment 1 Chris 2009-03-29 04:29:00 UTC 
Created attachment 131614 [details]
log from gvfsd

Notice that vsftpd does return success on the upload but only after gvfs ftp backend already does a list and apparently returns failure to OpenOffice.org.
Comment 2 Chris 2009-03-29 04:38:26 UTC 
This bug appears to be the same as bug 574968 which was originally thought to have been a caching issue and/or a pureftpd bug of renaming the file.
Comment 3 Chris 2009-03-29 04:41:16 UTC 
According to the ftp spec I am looking at you aren't supposed to do anything else after receiving a 1xx (eg 150) code until you get another code back... That would include the NOOP code that is being sent currently.
Comment 4 Chris 2009-03-29 04:44:25 UTC 

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