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 601726 - Connect to server password dialog could give more information
Connect to server password dialog could give more information
Status: RESOLVED DUPLICATE of bug 621583
Product: nautilus
Classification: Core
Component: general
2.28.x
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-12 18:16 UTC by Pedro Villavicencio
Modified: 2010-07-22 20:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Pedro Villavicencio 2009-11-12 18:16:09 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/480210

"Consider the use case where a user is attempting to connect to two different servers, with two different accounts, and two different passwords. This is completely possible, but if the user attempts this using book marks in the places menu, hitting both in quick succession, the user may not know which dialog is intended for which server/account/password"

http://launchpadlibrarian.net/35494047/Screenshot.png
Comment 1 Marcus Carlson 2010-07-21 21:56:57 UTC 
Is this for connection to ssh: / sftp:/ ? If so, this is a gvfs problem and is fixed in git master.
Comment 2 Michael Jones 2010-07-22 20:42:00 UTC 
I was the original poster on launchpad. I see this behaviour when using the ssh:/ back-end. If the problem is already fixed in source control, then I suppose this bug can be closed. 

However, I would recommend verifying that the problem doesn't also exist with other protocols.
Comment 3 Marcus Carlson 2010-07-22 20:57:16 UTC 
Thanks for the information Michael. I've tried smb: and ftp: and both of them show information of where you're connecting, but please create a new bug if you find a protocol that lacks information.

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