I have Chromium based Browsers

• Chromium-ungoogled
• Brave

on Slackware64-15.0 with XFCE. Chromium-ungoogled continually asked for a password complaining about 'access to the Default keyring' which it says is locked. XFCE uses Gnome keyring stuff.

I did a search, and tried the recommended solution, i.e. "rm ~/.local/share/keyrings/*" and Chromium-ungoogled stopped it's bellyaching, but Brave persists. After you remove the keyrings you have to enter & confirm a new password on next time you boot X.

~/.local/share/keyrings now looks like this Any ideas from the Desktop heads here? I could use one.

I hate these keyrings with a passion, that includes whatever KDE calls it Yet another reason I avoid Desktops.

But I would try this, it is from my notes when I had a RHEL Workstation at Work:

Install slackbuild seahorse and maybe seahorse-plugins.

In seahorse, in the "View" drop-down menu, select "By Keyring". On the Passwords tab, right click on "Passwords: login", and pick "Change password".

It was possible to leave the GNOME keyring password blank or change it. The 'rm' use to work, but I think RHEL changed something that stopped that from working.

The usual recommendation is to use the same password for your login and your keyring. That should (yes, should) unlock your keyring when you log in.

EDIT:

It's PAM that does this, and I'm aware that that's not set up by default on all distros.

Funny goings on here. I saw a reply this morning, but couldn't see it again, and LQ was showing my thread as having zero replies.

I did use the user password for the keyring. Anyhow, only chromium and Brave Browsers use the gnome keyring feature, AFAICT. Removing the gnome-keyring package altogether killed the issue. It was one of the options I saw this morning, that isn't in your replies. Very weird. As a solution, it had instant appeal.

Thankfully, I have gone away from the likes of Red Hat altogether, and intend to stay that way.

Slackware prides itself on being "Your distro - your way." So there are documented ways of changing the basic system choices, to wit:

• Init system - Sysvinit.
• X Server - Xorg or Wayland.
• Window managers - Kde or XFCE
• Sound - alsa & Pulseaudio.

But you can shoehorn in Systemd, pipewire, Gnome, Mate or whatever. It's not rigid, it's flexible. And you don't have to fight the system to do it.

Yes, I remember that reply also with me thinking "I did not know gnome-keyring was in Slackware" and I went looking and there it is

So either we both had the Hallucination or something odd is happening.

If Gnome keyring is uninstalled, how do Chromium, Brave, or Vivaldi store passwords, login information, or SSL certificates? Is it then stored unencrypted on the hard drive?

They seem not to store them, as I'm discovering. Palemoon manages just fine. I don't have Vivaldi any more.

I had to uninstall Gnome keyring because Google consistently asked for login credentials upon opening the browser. This issue only occurred with Slackware, not with Debian. Additionally, even without Gnome keyring, Vivaldi continues to save passwords from various forums. However, it remains unclear how Vivaldi stores these passwords. I couldn't find definitive information about it on the internet.

Another project that got too big for it's own good - Gnome, I mean.

The trouble in cherry picking such things, as in xfce using the keyring, is that gnome can add another dependency on without noticing, seeing as you're supposed to use all of gnome, not cherry pick it.