Bug 213954 - Using smb:// as custom location when connecting to server doesn't save info
Using smb:// as custom location when connecting to server doesn't save info
Product: Fedora
Classification: Fedora
Component: gnome-vfs2 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
Depends On:
  Show dependency treegraph
Reported: 2006-11-03 17:13 EST by Brian C. Huffman
Modified: 2015-03-03 17:31 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 12:41:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian C. Huffman 2006-11-03 17:13:26 EST
Description of problem:
Using smb:// as custom location when connecting to server doesn't save info such
as the domain name or your password even if you click "save in keyring."  I
realize that you can (and probably should) use a service type of "Windows
Share", but this used to work (and should, I think).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Select Places-> Connect to Server
2. Select Custom Location
3. Specify a URI of the form smb://host/share
4. Type in domain and password, click on save password in keyring
5. Next time you open that vfs share, it should only require you to open your
Actual results:
Forces you to type domain name and password every time.

Expected results:
it should only require you to open your keyring

Additional info:
Comment 1 Alexander Larsson 2006-11-08 06:26:37 EST
Thats very weird, how you type in the uri has nothing to do with how the keyring
and auth works.
Comment 2 Bug Zapper 2008-04-04 00:24:01 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 3 Bug Zapper 2008-05-06 12:41:21 EDT
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.