You are not logged in.
Every time I start chromium I get a useless prompt for a keyring password that has to be canceled multiple times to get rid of it. There is no such thing as a keyring password on my system, as there is no keyring. Unless chromium creates it, in which case I want to stop it from even creating it. So far, all solutions found by google search have no effect.
Copying /usr/share/applications/chromium.desktop to ~/.local/share/applications and adding the '--password-store=basic' option to the Exec line does nothing. Creating a file called chromium-flags.conf file under .config/chromium and adding the option that that does nothing.
What does it take to tell the current version of chromium to not bother with encrypted keyrings?
Last edited by Micronaut (2020-04-08 01:19:56)
Offline
Try from command-line. That helped me back then. To see, if your desktop or config file were actually used or not!
$ chromium-browser --password-store=basic
See https://forums.gentoo.org/viewtopic-p-7951970.html#7951970
Otherwise, what chromium packages are installed? Are there some chromium packages indicating connections to libsecret or gnome-keyring? They should be uninstalled. That are the solutions from Gentoo.
Offline
Gentoo? I'd expect Gentoo to recommend you recompile chromium with different flags.
When I was experimenting with it, I found that chromium also cannot connect to audio on Discord. It just sits there "waiting to connect" -- forever. Dunno if that's a reflecting of how bad Discord is, or chromium. I've heard that Discord is a pretty hairy mess written entirely in Javascript and run via Electron even on tablets or desktops. Ergh... so I switched back to Firefox. Which at least does work.
But you never know when Mozilla will do something annoying with Firefox. So I would like to have alternatives to Firefox, and I guess I'll go back and struggle with chromium some more soon.
Offline
Yup, Gentoo recommends compile flags. Debian, or any other binary distro, recommends packages to install/uninstall. In the end, it is all the same.
Offline
I had the same problem with Opera on another distro. It's very frustrating. I didn't find a solution.
In fact, I've been put off installing Brave after seeing this:
sudo apt-key --keyring
https://brave-browser.readthedocs.io/en … html#linux
That term keyring in there makes me think it would be deja vu all over again.
Devuan Daedalus 5.0 | MX Linux 23 | Slackware 15
Offline
dont use google chromium, sorry couldnt resist.
Might be something to do with gnome-keyring maybe?
https://wiki.archlinux.org/index.php/GNOME/Keyring
Last edited by HevyDevy (2020-06-25 15:52:54)
Offline
I'm guessing the present Opera is based on Chromium, which would explain the problem I had. I know they 'changed engine' after Opera 12, probably to Chromium by the looks of it.
Devuan Daedalus 5.0 | MX Linux 23 | Slackware 15
Offline
I guess it's a Chrome/Chromium issue as I have the same problem with Skype, which, surprise-surprise, also uses Chromium engine.
Last edited by Copper36 (2020-08-09 19:35:15)
Offline
Every time I start chromium I get a useless prompt for a keyring password that has to be canceled multiple times to get rid of it. There is no such thing as a keyring password on my system, as there is no keyring.,,
Chromium doesn't do that for me. But then again, I don't store any usernames and passwords in Chromium. Perhaps clearing all browsing data under Privacy and Security may solve this issue but it will clear all your saved passwords as well.
As an aside, I almost always use Firefox except for certain sites like jitsi.org conferencing which is more stable under Chromium.
Offline