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 626389 - SSH Port not shown when editing server connection, cleared at "OK" button.
SSH Port not shown when editing server connection, cleared at "OK" button.
Status: RESOLVED DUPLICATE of bug 621756
Product: gnome-commander
Classification: Other
Component: networking
1.2.x
Other Linux
: Normal normal
: 1.2.9
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2010-08-08 20:03 UTC by Marco Freudenberger
Modified: 2011-09-14 20:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Marco Freudenberger 2010-08-08 20:03:35 UTC
When creating a new server connection through SSH (SFTP) and editing the entry, the port is not shown in the gui. 
When pressing "OK" without the port shown, it is removed from the server address entry and the default port is used.
However: the port seems to be stored and used at later times when adding it to the server address (e.g. "my.server.com:9876"). In this case, it is also not shown when editing the stored server connection, but it seems to be stored and used.

Also, very strange behaviour encountered while trying to work arround the bug:
 
I've created two connections using the same server and port
- ConA using the server:port notation in the "server" edit field
- ConB using only the server name in the server edit field and the port in the "port" edit field.

Closing and reopening gnome commander, ConB doesn't work; ConA works. Closing ConA and trying to open ConB --- now ConB WORKS (until gnome-commander application closed and opened again...). Something smells fishy with the way the port is handled...

Version: 1.2.8.5, ubuntu 10.04, 32 bit
Comment 1 Marco Freudenberger 2010-08-08 20:49:26 UTC
besides my more detailed description and the "strange behaviour encountered while working arround", this seems to be *partly* a duplicate to 621756; sorry, didn't find this when searching through the  bug list...
Comment 2 epiotr 2011-09-14 20:37:05 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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