I don’t set a password for keyrings, and everything works fine until the next monthly update most of the time. Some updates don’t cause the problem.
So in the directory “.local/share/keyrings”, I see the files :
default
Trousseau_de_clés_par_défaut.keyring
Trousseau_de_clés_par_défaut_1.keyring
Trousseau_de_clés_par_défaut_2.keyring
etc., one file per login. ()
So I delete the directory and the next time I log in, I don’t enter a password and everything goes back to normal until the next update.
This has been going on for a while now, I can’t say if it’s with version 43, 42 or earlier… and I’ve been looking for a solution ever since. Now I’m asking.
Chromium based browsers use the system keyring to store the encryption key for passwords saved in the browser (even if you don’t use this feature). The system keyring is locked by default until you login with your user password. The most common complaint of this system are chromium based browsers asking for the user password when folks use automatic login. Nobody sees your user password - it simply unlocks the system keyring and then the chromium based browser can then retrieve its encryption key.
Firefox I believe stores its encryption key for the same purpose in your firefox profile.
The Gui to configure your keys is called seahorse. From the information above, it looks like that you are using auto login? Could that be?
It also looks like that the browser you are using is chromium based like Google Chrome, Brave etc.
You can try to open seahorse click on the login key, and enter your actual login password (change password). It could also be, that when you upgrade the browser it just updates its own key?
So when you delete this keys manually, they will be created automatically and need to be actualized with your software/browser installed.
Please try the above steps and give feedback if setting the password manually solves the issue.
Thank you for your reply. I am familiar with Seahorse and I do use automatic login. I had already tried this tip (I searched extensively before asking for help here).
I don’t use Chrome, but Firefox, among others. The first to use keyrings is a utility from my cloud storage provider.
So yes, it uses keyrings to save the password. But that’s not the problem, because once I delete the keyrings backup directory “.local/share/keyrings,” I enter my password and everything works fine for a while.
Then, when a component is updated (I don’t know which one, because the updates are relatively large), the problem recurs and I have to repeat the process.
I looked at the keyrings maintainer’s directory and found nothing about this problem, and since there were many requests and incident reports, I didn’t want to create my own before I had more information.