GNOME Bugzilla – Bug 520399
Nautilus can't access non-listed (hidden) ftp directory
Last modified: 2009-08-07 19:37:28 UTC
This is not crucial for my daily ftp-ing, but I found a server that doesn't work at all with the gvfs backend (and not even gnome-vfs). "21/tcp open ftp ProFTPD" If you want to look at it say so, and I will send testing account credentials to your private email. My version is 0.1.11-0ubuntu1.
If that still happens with current nautilus, it would be nice if I could get an account. Even though ProFTPD is supposed to work according to other people.
Still no cookie. I sent you the login details to otte {} gnome.org. Perhaps a weird config on their side ...
Ok, there's multiple issues involved here. 1) Nautilus always starts in the root directory of mounts. If you may not access the root directory, Nautilus doesn't let you access the mount via clicking on it. 2) Nautilus queries the file info of directories before listing them. The ftp backend does produce file infos by listing the parent directory. So we fail that and Nautilus doesn't access it. 2b) The reason Nautilus fails is that the failing code returns G_IO_ERROR_EXISTS instead of G_IO_ERROR_PERMISSION_DENIED. Problem here is that ftp servers report code 550 for all error messages. We should probably try to parse the "informational" message to get a better error message.
*** Bug 551822 has been marked as a duplicate of this bug. ***
Created attachment 132272 [details] [review] Completely untested patch possibly fixes issue 2. Extend the create_file_info function (used by nautilus when querying file information) to not only LIST, but also try_cd and issue SIZE if feature is available and make up the details for hidden files/directories.... Beware! Completely untested.... need to run. Will look more at this later.
I applied the patch. It should be in gvfs 1.2.2 or later. The patch doesn't solve the "Nautilus starts in home directory" problem, but it allows to manually cd into readable directories using the location bar now.
Thanks Andreas. This patch lets us work around the "Nautilus starts in home directory" problem as Benjamin says. As this bug is marked "resolved fixed" is there a separate bug for "Nautilus starts in home directory"? I've not been able to find one... and that's ultimately what needs fixing. (I appreciate not an easy fix re comment 3)
Actually I still cannot log into the ftp that this bug report originally was about. why was is closed again?
Because you are supposed to manually browse to ftp://ftp.example.com/path/that/is/accessible in the location bar and we concluded this was good enough to close this bug. And there should be a bug for the home directory problem, but I fail to find it.
Okay. I logged in with lftp and let it show the pwd: ftp://<user>@ftp.alice-dsl.net/%2FWA so %2F is url encoded for / (slash) neither of these worked in Nautilus: - Could not display "ftp://ftp.alice-dsl.net/WA" Error: The file is not a directory Please select another viewer and try again. - or "ftp://ftp.alice-dsl.net//WA" -or "ftp://ftp.alice-dsl.net/%2FWA" what am I doing wrong?
I blame Nautilus. gvfs-ls ftp://ftp.alice-dsl.net//WA works fine here. Could you open a new bug against Nautilus about that?