Keyring "Default" asked to be created at every start up

[EliasAOlsson]

System details

Lenovo Thinbook 15 G3

What's wrong?

I cannot pinpoint exactly what change resulted in this bug/misconfiguration but I believe it was after I tried installing proton VPN. I had some problems with the program (maybe because I also have mullvad installed) and decided to uninstall it. After that, I simply updated the system later and rebooted.
After the reebot, I got a prompt asking for a "default keyring", getting a prompt also for protonbridge and for brave. On top of that, I also lost all my "logins" in Brave and when login in again I get notified as if it was a completely new login (not really than important to mention here maybe).

I tried installing and managing the keyrings with Seahorse but I'm no expert and have not managed to not get the prompt each time (also when setting the keyring as a blank). I cannot manage to maintain my logins opened in brave neither, which is kind off annoying. I have also tried to open older snapshots, which did not really help with the problem.

I'm well aware that this might not be a bug, but it really appeared out of nowhere after updating the system. Thanks for any help!

[EliasAOlsson]

I have managed to learn how keyrings work and fixed the issue for myself. I guess I should still leave this here because the system got dis-configured after updating.

[kromsam]

Could you share with us how you fixed this issue?

[dreadvimfantail]

I cannot pinpoint exactly what change resulted in this bug/misconfiguration but I believe it was after I tried installing proton VPN.

This started after I installed Proton VPN as well.

[dreadvimfantail]

I was able to get gnome-keyring-daemon to stop showing up on reboot. Here are the steps that I took. Keep in mind that I am also using LUKS. I am also using Proton Bridge which I suspect is the application that was requesting the keyring. Here are the steps I took:

1. Installed seahorse and saw there are multiple Default Keyrings associated with Proton Bridge.
2. Checked ~/.local/share/keyrings and saw

default
Default_keyring.keyring
Default_keyring_1.keyring
Default_keyring_2.keyring
login.keyring
user.keystore

3. The file default is a text file with a single line: Default_keyring.
4. I ran echo "login" > ~/.local/share/keyrings/default.
5. Changed Login password in seahorse to be blank.
6. Removed unnecessary .keyring files. I don't recommend doing this! You'll have to re-authenticate any applications, but it's not world ending.

This seems to work, but on login, Proton Bridge appears and requires me to login each time instead of automatically logging in (presumably because I deleted the keyring file that managed it). I'm using the Docker file for Proton Bridge, which may complicate the matter further.

I don't know if this will work for everyone, but it seemed to work after changing the default file in step 4 and rebooting.

Hope this helps!