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 331583 - No default port and directory in Connect to Server: SSH (and others )
No default port and directory in Connect to Server: SSH (and others )
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: general
2.14.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-17 18:16 UTC by Lakin Wecker
Modified: 2012-05-03 04:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Lakin Wecker 2006-02-17 18:16:40 UTC
From downstream, launchpad:
https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/30039/

"Connect to Server: SSH asks user for target port and directory. Normal end
users don't usually know these.

The port is normally 22/tcp, and nautilus uses this automatically if it is left
empty. However, there is no way for user to know that it can be left empty.
Suggestion: have text "22" in the port field by default, when the dialog is opened.

Directory to connect to is empty. If left empty, it will connect to root
directory "/". In many big systems, user home directories are not directly under
"/home/", but are separated to many directories. In practice, this means that
user must use command line "ssh" and "pwd" first to find out his home directory
before using "Connect to Server".

Suggestion: Connect to user home directory by default if the field is left
empty. Have small text under the directory field: "Defaults to your home
directory if left empty. "  "

Other information:
Comment 1 Tero Karvinen 2006-02-17 22:06:32 UTC
Invisible characters cause error in "Connect to Server". 

In the typical use scennario above, users typically copy-paste the home directory to "Connect to server" dialog. Copy pasting selects the trailing newline, which causes weird error when actually trying to connect. Suggestion: ignore invisible characters in "Connect to server" dialog. 
Comment 2 Sergej Kotliar 2006-04-04 22:53:25 UTC
Tero: I suggest filing a separate bug report for that.

Confirming the bug for 2.14. Not sure it should enter the values, but some notification of it being an optional field should be there.

Perhaps even moving it all into an "> Advanced " widget?
Comment 3 Tero Karvinen 2006-04-08 14:24:25 UTC
"> Advanced" is a good idea! SSH should be the default, better than FTP, the current default. The dialog could be like this:

User Name:
Server: 
> Advanced
Folder: 
(Defaults to user home directory)
Port: 22
Name for connection: 
(Defaults to username@server)

- The advanced config is normally hidden, only the advanced button is shown. 
- User before server, consistent with cli ssh behavior and written url user@host
- Default port should be written on field, consistent with Preferences: Printing: New printer
- Is it necessary to ask for a name for connection? Of the 100+ I have shown this, most call first server something like "server1", the second "server2" and then forget which is which. They also think that the choice of name somehow affects the connection
Comment 4 André Klapper 2011-09-08 07:49:07 UTC
Is this still an issue in a recent version, such as 3.0 or 2.32?
Comment 5 Cosimo Cecchi 2012-05-03 04:14:43 UTC
This has been long fixed.