Chromium still ask for keyring after boot

[sarniva]

Specification:-
AMD
Omarchy 3.2.0

Have I missed any migration or anything ?
Chromium and other browser still asks for keyring after every boot.
Any solution?

[sspaeti]

I have the same, after each boot, but with Brave (tough Chromium might be running too). I invested quite some time or debugging, like deleting all keyring files, or delaying Brave startup, but no luck so far.

The logs say

  gnome-keyring-daemon: keyring was in an invalid or unrecognized format:
  /home/sspaeti/.local/share/keyrings/Default_keyring.keyring
  Impact: Keyring fails to unlock on login, requiring Brave re-authentication each boot.

But the format should be alright, as it's just created new by Brave when starting up.

[4ndri]

this might be related:

• keyring isn't being unlocked at login, so apps can't access stored credentials and create new keyrings instead #3331

this comment helped me: #3331 (comment)

[sspaeti]

this might be related:

• keyring isn't being unlocked at login, so apps can't access stored credentials and create new keyrings instead #3331

this comment helped me: #3331 (comment)

Thanks, I tried it, but didn't for me.

I think I found the problem, it's Brave as I have it autostart at the beginning, it conflicts with authentication method. When I add brave --password-store=basic it seems to work, at least the last two restarts.

Here's my commit on my dotfiles: sspaeti/dotfiles@dcd7562