Gnome-keyring dependency and chromium browsers

[Quiksilver]

So I just did a full upgrade and now I get prompted to unlock the keyring for Brave browser everytime its launched.

In the past when I was distrohopping another distro that had xfce I would get that same prompt with Ungoogled-chromium and also Vivaldi which are both chromium based.
Its weird considering I never even use a browser keyring password manager I dont get why it prompts this.

Anyway the fix always used to be purge gnome-keyring however this doesn’t seem to be the best choice.

When you type sudo apt purge gnome-keyring it will show the other dependencies to remove are kicksecure-desktop-environment-essential-xfce and other Kicksecure specific ones so obviously I chose NOT to go forward.

The only fix in the meantime that is better is to add the chrome flag --password-store=basic which will ingore using GNOME keyring or kwallet (KDE).

So you would edit your launcher Exec=/usr/bin/browser --password-store=basic for the browser application or you could edit your /usr/share/application/browser.desktop file for desktop file but this might get updated with new updates so launcher seems like the safer bet.

Back to the point why is gnome-keyring dependency needed and could something be added to Kicksecure like above to automatically fix this pesky issue or to the wiki regarding chromium unlock keyring prompt with gnome-keyring.

Solution add the chrome flag --password-store=basic

[Patrick]

@Quiksilver

why is gnome-keyring dependency needed

You can follow the history of that here:

Error storing passphrase in keyring (The name org.freedesktop.secrets was not provided by any .service files)

After booting the ISO → Xfce desktop → double click on “17 GB Encrypted” (from a previous installation) → enter password → save password permanently. Failed to mount “rootfs” Error storing passphrase in keyring (The name org.freedesktop.secrets was not provided by any .service files) Since we’re already installing KeePassXC by default, it might make sense to use KeePassXC as a org.freedesktop.secrets provider. Here is a promising looking (untested by me) guide: https://c3pb.de/blog/kee…

add `gnome-keyring` to `kicksecure-desktop-environment-essential-xfce`

@Quiksilver

When you type sudo apt purge gnome-keyring it will show the other dependencies to remove are kicksecure-desktop-environment-essential-xfce and other Kicksecure specific ones so obviously I chose NOT to go forward.

This is documented here:

Debian Packages

@Quiksilver

Anyway the fix always used to be purge gnome-keyring however this doesn’t seem to be the best choice.

Feel free to experiment with removal of gnome-keyring. This should be easily possible thanks to dummy-dependency, Removal Instructions.

sudo dummy-dependency --yes --purge gnome-keyring

@Quiksilver

So you would edit your launcher Exec=/usr/bin/browser --password-store=basic for the browser application or you could edit your /usr/share/application/browser.desktop file for desktop file but this might get updated with new updates so launcher seems like the safer bet.

Even if we find a technical solution to do this reliably by default [1], I am not sure we should change chromium default keystore settings. Comments welcome.

---

[1] We would probably have to solve the stackable wrappers issue.

Kicksecure/proposals/blob/master/634-stackable-wrappers.md

Stackable Wrappers