FTP connection not available/doesn't work

Bug #546659 reported by Šimánek
100
This bug affects 21 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: nautilus

In Ubuntu Lucid 10.04 dev/beta Nautilus cannot connect to FTP server

nautilus:
  Installed: 1:2.29.92.1-0ubuntu4
  Candidate: 1:2.29.92.1-0ubuntu4
  Version table:
 *** 1:2.29.92.1-0ubuntu4 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Going to File > Connect to server only provides option for 'Custom Location'.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Šimánek (jasonsimanek) wrote :

* Is this reproducible?

Yes. Every time I try to connect to any FTP server via Nautilus (in Ubuntu Lucid Beta) I am not allowed to connect. In fact, Nautilus doesn't even attempt to connect because the entire process of dialogs that previously (Ubuntu </=9.10) walked me through connecting to an FTP server has been changed and options like 'Public FTP' and 'FTP with Password' are no longer available. As I said:

Going to File > Connect to server only provides option for 'Custom Location'

I don't know if this is an intentional change in how Nautilus works or if this is some kind of mistake.

Revision history for this message
Paolo Stancato (paolodoors) wrote :

I'm having the same issue

Revision history for this message
Paolo Stancato (paolodoors) wrote :

This is the error I get:

Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Seleccione otro visor e inténtelo de nuevo.

Revision history for this message
Jason J. Herne (hernejj) wrote :

I can confirm that using Lucid updated at of April 1st I am not having this problem. I'm not sure about before today. I do have a FTP and Public FTP available to me (as well as several other options) in Nautilus.

I wonder what is different in your environment that is keeping you from having those options?

Changed in nautilus (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Šimánek (jasonsimanek) wrote :

Just did the latest updates for Lucid Beta 1. I also tried to delete what I think are my nautilus preferences. I also launched nautilus via sudo. Nautilus consistently only offers the useless 'Custom Connection' option when attempting to 'Connect to Server...'. I don't think it's related to my preferences.

Revision history for this message
Aethralis (aethralis) wrote :

I'm seeing the normal 'Public FTP' and 'FTP with Password' lists, but am unable to connect to any server receiving "Error: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Please select another viewer and try again." error message.

gFTP works as intended though, so this is problem in nautilus end.

Revision history for this message
Andrew Keyes (akeyes) wrote :

Experiencing the same (or perhaps similar) problem after upgrading to 10.04. Unable to connect at all, but connecting via ftp on the command line works perfectly.

Could not display "ftp://......@..................".
Error: Unexpected end of stream
Please select another viewer and try again.

Revision history for this message
Šimánek (jasonsimanek) wrote :

I tried the 10.04 livedisc on my laptop and the FTP in Nautilus worked as expected, so I just backed up and reinstalled. There must be a bug in the upgrade process.

Revision history for this message
Nuño (niglesi) wrote :

I can confirm that this is happening also in my computer.

Ubuntu 10.10
Gnome 2.32.0
Linux 2.6.35-28

This bug has been here for a long time...
Any help will be apreciated...

Revision history for this message
David-nnucomputerwhiz (david-nnucomputerwhiz) wrote :

This started happening for me. Using Ubuntu 11.04. Everything worked fine after the update and used ftp and sftp connections all the time. It seemed to break after I installed the Thunar file manager but I can't confirm that was the cause for certain. "Connect to server " just has the custom location option. Existing bookmarks give the error "Nautilus cannot handle 'sftp' locations." Get the error "Natilus cannot handle 'network' locations when clicking on network." and "Nautilus cannot handle 'computer' locations." when clicking on the computer icon. It's like Nautilus doesn't know about anything except normal file locations.

I'd be happy to troubleshoot this as much as needed just tell me where to look.

Revision history for this message
Ramy (ramy-daghstani) wrote :

I can confirm this with a fresh install of ubuntu 11.04.

However, I had backed up some files from my old home folder from an old ubuntu install (10.04?) and brought them back in after the fresh install, and whatever files that take care of remembering ftp locations was also a part of that because when I first connected through ftp to one of my servers, it worked fine, but later on I had changed my ftp password, after which a prompt would appear in nautilus to enter the new password to get into the site - at this point, FTP was no longer functional.

Revision history for this message
Mörgæs (moergaes) wrote :

Is this still a problem in 13.10?

Revision history for this message
Mörgæs (moergaes) wrote :

Closing due to age.
If a similar bug appears in 13.10 please open a new report.

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.