Binary package hint: nautilus
When opening an SMB share (using the URL smb://user@server/share), Nautilus pops up a password dialog with the fields "domain" (pre-filled with "WORKGROUP") and "password" and the standard "remember password" radio buttons.
After filling in domain name and password and selecting "remember password forever", the share is mounted. If I now disconnect the share and try to reconnect it, the password dialog appears again - basically disregarding my request to remember the password.
If I go into the passwords and encryption keys application (seahorse) and look for the SMB password, I can see it is stored correctly, including the correct domain name under the "details" tab.
I believe the problem is that Nautilus does not know which domain to login under as the domain is not part of the SMB URL, and so fails to locate the correct stored password. If I omit the user part of the URL and if my local user name is not identical to the remote user name, then the password dialog would also include a user name entry which would probably also complicates things.
I think that Nautilus should lookup all the keys that match the details provided in the URL (whether its just protocol and server or protocol, user and server) and if only one stored password is listed then use that automatically. If there are more then one then its a UI issue that has to be though out: show a list? show the password dialog with one password pre-populated?
I also think that its a shame that nautilus does not store the share address in the keyring as people may want to provide different credentials for different shares on the same server, but that is a different report and one that does not interest me personally at this time.
ProblemType: Bug
Architecture: amd64
Date: Tue Oct 27 12:59:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.28.0-0ubuntu7
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-14-generic x86_64
Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https:/