From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5)
Description of problem:
Not every ftp server has a default working directory upon logon.
When gFTP connects and logs on it issues a PWD command.
When there is no default working directory, gFTP sees return code 450
and promptly disconnects, saying it will try again 30 seconds.
This is wrong. gFTP should remain connected, and allow the user to use
the drop down menus to manually change directory.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ftp to: sruvm.sru.edu
Actual Results: Looking up sruvm.sru.edu
Connected to sruvm.sru.edu:21
220-FTPSERVE IBM VM V2R4 at SRUVM.SRU.EDU, 12:59:21 EST THURSDAY 01/20/05
220 Connection will close if idle for more than 5 minutes.
230-ANONYMOU logged in; no working directory defined
230 File pool SERVER5 unavailable or unknown;
215-VM/ESA Version 2 Release 3.0, service level 9902
VM/CMS Level 14, Service Level 902
215 VM is the operating system of this server.
200 Representation type is IMAGE.
450 No current working directory defined
Invalid response '4' received from server.
Disconnecting from site sruvm.sru.edu
Waiting 30 seconds until trying to connect again
Expected Results: gFTP should have left well enough alone and stayed
connected after getting the 450 from the PWD command.
I'm setting this as "high severity", not because it crashes etc, but
because it diminshes the usefulness of the program... there's no way
to effectively use the ftp server if the server doesn't have a default
4xx erros from FTP means the condition is temporary and may be tried
again..... so gFTP must not disconnect from the server in those cases.
I'm not sure how this happened... but this is an exact copy of bug
145699. Since this one is assigned now, and the other is not, 145699
should be deleted, or at the very least marked as a duplicate of this one.
Sorry for the confusion... like I said.. I don't know how that
*** Bug 145699 has been marked as a duplicate of this bug. ***
Problem also exists in gftp-2.0.18-0.FC3
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Change from FC3 to FC5, affected software versino is gftp-2.0.18 (same version
as 2005-04-26 above in comment #3)
Fedora Core 5 is no longer maintained. Is this bug still present in Fedora 8?
Yes, the problem still exists in Fedora 8... I changed the version FC version to 8.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Go ahead and flag this as WONTFIX. I've been tracking this since FC3, FC10 is out today... and I don't use gFTP any more, haven't for a long time.
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.