View previous topic :: View next topic |
Author |
Message |
cfgauss l33t
Joined: 18 May 2005 Posts: 688 Location: USA
|
Posted: Sat Aug 06, 2016 4:21 pm Post subject: New chromium requires keyring password |
|
|
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]
Last edited by cfgauss on Mon Aug 08, 2016 11:28 pm; edited 4 times in total |
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
|
Back to top |
|
|
cfgauss l33t
Joined: 18 May 2005 Posts: 688 Location: USA
|
Posted: Sat Aug 06, 2016 5:11 pm Post subject: |
|
|
Ant P. wrote: | https://forums.gentoo.org/viewtopic-t-1047930-highlight-chromium+kwallet.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: | ** 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. |
|
Back to top |
|
|
The Doctor Moderator
Joined: 27 Jul 2010 Posts: 2678
|
Posted: Sat Aug 06, 2016 8:59 pm Post subject: |
|
|
Check emerge -pv www-client/chromium and remove the features you don't want, like gnome-keyring _________________ First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
Back to top |
|
|
cfgauss l33t
Joined: 18 May 2005 Posts: 688 Location: USA
|
Posted: Sat Aug 06, 2016 10:10 pm Post subject: |
|
|
The Doctor wrote: | Check emerge -pv www-client/chromium and remove the features you don't want, like gnome-keyring |
Code: | $ 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? |
|
Back to top |
|
|
The Doctor Moderator
Joined: 27 Jul 2010 Posts: 2678
|
Posted: Sun Aug 07, 2016 8:10 am Post subject: |
|
|
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. _________________ First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
Back to top |
|
|
Lars Apprentice
Joined: 06 Feb 2003 Posts: 171 Location: Germany, near baltic sea
|
Posted: Sun Sep 09, 2018 12:50 pm Post subject: FYI: chromium 69 without password question |
|
|
Start google-chrome-stable (version 6 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 _________________
Quote: | Alles was nicht einfach ist, ist entweder falsch oder zu kompliziert. |
V.Glazounov |
|
Back to top |
|
|
Blind_Sniper Guru
Joined: 20 Apr 2018 Posts: 336
|
Posted: Sun Sep 09, 2018 9:15 pm Post subject: |
|
|
try to add --password-store=basic option to command line when launching chromium:
Code: | chromium --password-store=basic |
it works for chrome, should work for chromium too |
|
Back to top |
|
|
martinkunev n00b
Joined: 21 Mar 2012 Posts: 4
|
Posted: Mon Jun 07, 2021 10:31 pm Post subject: |
|
|
Disabling "Allow Chromium sign-in" from chrome://settings/ worked for me (maybe not exactly the same problem, but related). |
|
Back to top |
|
|
|