Prompt to unlock user keyring, using auto login

[kelean]

Hi I have just installed Fedora-19 a few days ago. I have enabled auto login. Everything is working very well but when I open Chrome I get a prompt that says user keyring did not get unlocked at start up. It has happened a couple of times with other things but can't remember what they were.

How can I stop this? I tried to search for a solution but could not find one. I also searched for some documentation but did not find what I was looking for. Any help or push in when right direction will be most appreciated.

Thank you Kelean.

[pinkfloyd]

I used seahorse to disable it. Worked for me.

[pinkfloyd]

http://www.fandigital.com/2012/05/ho...in-ubuntu.html

[kelean]

Thanks for the reply pinkfloyd. I looked at seahorse and the link you posted. What the site showed me was different than what keys and passwords looked like when opened. So I need to study this before I make any changes. Besides that I am not sure what keyring to disable. It is only a an inconvenience if I just cancel it everything still works.

[pinkfloyd]

You have to look closer down the page for ubuntu 12.10. In seahorse you check "by keyring" in the view menu.

The interface of Seahorse in Ubuntu 12.10 is a bit different from previous version. After installing the latest Seahorse, open it, then to show the login password, select "View" menu ==> check "By keyring" (see the screenshot above), then right-click "Login" password on the sidebar. Then the next steps is similar to the above: enter your current password but leave the new password blank, and click OK to confirm unencrypted keyring.

[kelean]

Thanks for the explanation pinkfloyd. I fixed it.

Thanks again.

[anteb]

When using google chrome for the past 2 months there was an error message being constantly displayed. The "Unlock 'Default' Keychain" is displayed upon every time a site with a login page is accessed. This is extremely annoying .

The best solution that i found is the easiest. Edit the application launcher or from the command line launch chrome with the following parameter:

 --password-store=basic

Essentially what this parameter does is tell chrome to use its own build in password storage and nothing else.


So your application launcher cmd should look something like this:

/usr/bin/google-chrome-stable --password-store=basic %U

Are wondering why this works and what is up with google chrome wanting access to your keychain? I was, and i found out that eventually google chrome will use the native linux user encrypted keychain for storing passwords. Right now google chrome wants to check if there is a password stored in your linux keychain to access and login to the login page that it was directed to. The part where google chrome works seemlessly with the native linux keychain is not implemented yet for stable versions of chrome. It is already implemented on lasted chromium version from what i read. Basically the current stable versions of chrome have no automatic method of accessing your linux user's keychain. This is a feature that is being integrated into future releases of chrome from google. Right now this functionality is broken and bloody hell annoying. That is whay you have to unlock the keychain manually for google chrome even though the keychain is probably even already unlocked. Just bypass this entirely by telling google chrome not to use this

[498201]

I used seahorse to disable it. Worked for me.

Thank you so much for this, this worked like a charm for me!

[bycara]

Thank you anteb. It was driving me crazy.