New chromium requires keyring password

[cfgauss]

I'm running KDE and chromium-53.0.2785.34. With this new chromium version, a window appears every time I boot the browser demanding "Enter password for keyring 'Default' to unlock." My login password doesn't work but Cancel allows chromium to function. There is a USE flag gnome-keyring for chromium which I have not enabled.

How do I get rid of this annoying keyring request?

Any debugging hints will be gratefully received.

[WORKAROUND]
This is not a solution. The gnome-keyring password for the Default keyring was unknown to me and certainly wasn't my login password, so I deleted ~/.gnome2/keyrings/default.keyring. The next time I booted chromium the gnome-keyring process asked me to choose a password for a new Default_keyring keyring. Now the first time chromium boots I am able to unlock the keyring (since I now know the password) and subsequent boots during that KDE session don't require further passwords.

However, I'd love to be able to use chromium without gnome-keyring.
[/WORKAROUND]

[Ant P.]

https://forums.gentoo.org/viewtopic-t-1 ... allet.html

[cfgauss]

https://forums.gentoo.org/viewtopic-t-1 ... allet.html

Setting CHROMIUM_FLAGS="--password-store=basic" in /etc/chromium/default didn't work for me. Also, starting chromium from the command line with chromium-browser --password-store=basic still produces the keyring pop-up but with this perhaps-relevant error (among others):

Code: Select all

** Message: Remote error from secret service: org.freedesktop.Secret.Error.IsLocked: Cannot create an item in a locked collection

Any debugging hints will be gratefully received.

[The Doctor]

Check emerge -pv www-client/chromium and remove the features you don't want, like gnome-keyring

[cfgauss]

Check emerge -pv www-client/chromium and remove the features you don't want, like gnome-keyring

Code: Select all

$ emerge -pv www-client/chromium

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] www-client/chromium-53.0.2785.34::gentoo  USE="cups hangouts (pic) proprietary-codecs pulseaudio system-ffmpeg tcmalloc widevine -custom-cflags -gn -gnome -gnome-keyring (-gtk3) -kerberos (-neon) (-selinux) {-test}" L10N="-am -ar -bg -bn -ca -cs -da -de -el -en-GB -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -vi -zh-CN -zh-TW" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

Why does chromium invoke gnome-keyring on startup if the enabled USE flags don't include gnome or gnome-keyring?

[The Doctor]

That is a good question. It doesn't on my system and the only differences between useflags is pulseaudio tcmalloc and widevine.


Was USE="genome-keyring" on in the past? Maybe check a new user or move the .config/chromium/ directory to see if a clean start solves the problem.

[Lars]

Start google-chrome-stable (version 68) or the beta version google-chrome-beta (version 69) with parameter --password-store=basic and the keyring will not ask for a password. If this not work as expected, remove the directory ~/.config/google-chrome-* and start chrome again.

The make.conf USE flag "gnome-keyring" is not used any longer.

JM2C

[Blind_Sniper]

try to add --password-store=basic option to command line when launching chromium:

Code: Select all

chromium --password-store=basic

it works for chrome, should work for chromium too

[martinkunev]

Disabling "Allow Chromium sign-in" from chrome://settings/ worked for me (maybe not exactly the same problem, but related).