Chrome harasses me for a keychain password at startup

This problem has a long history and you can fiddle around with gnome-keyring if you want, but I found that the easier solution is to set that prompt's password to blank, such that it won't ask you anymore:

  1. rm ~/.local/share/keyrings/* (you may want to check/backup these files first, if you're not on a fresh install, e.g., cp -r ~/.local/share/keyrings ~/keyrings-backup)
  2. Restart Chrome
  3. When prompted to create a keyring, continue without entering a password. (Turns out you would have been okay if you did this the first time.)

Don't know is this question is still relevant but I found a solution that works for me. I am running Debian Jessie i386. Use the XFCE desktop and gdm3 display manager. What I found was that going into the Applications Menu Settings>Session and Startup>Advanced and selecting Launch Gnome Services on Startup cured the problem. Not sure how this would be effected on other distros but it works on Debian Jessie.


I do not know what distro you are on, but I would create a script in ~/bin and call it chromium (for Debian) or chromium-browser (for Ubuntu). Be sure to adapt the script according to what Chromium is called on your distro:

#!/bin/bash
/usr/bin/chromium-browser --password-store=basic "$@" 

For Google Chrome, you can create another script in ~/bin and call it google-chrome-stable with the following:

#!/bin/bash
/usr/bin/google-chrome-stable --password-store=basic "$@" 

The above scripts will use the argument --password-store=basic for every instance when you launch one of the two programs.

From this source:

--password-store Specifies which encryption storage backend to use. Possible values are kwallet, kwallet5, gnome, gnome-keyring, gnome-libsecret, basic. Any other value will lead to Chrome detecting the best backend automatically. TODO(crbug.com/571003): Once PasswordStore no longer uses the Keyring or KWallet for storing passwords, rename this flag to stop referencing passwords. Do not rename it sooner, though; developers and testers might rely on it keeping large amounts of testing passwords out of their Keyrings or KWallets.