Hello, I am using Seahorse/Keys and Passwords to store passwords. There is already a keyring named “Login”, but it contains some other data that seems necessary to the operation of Google Chrome, and it is encrypted with the password I use to log into my computer. I decided not to touch this, and created a new keyring called “Login Passwords”, locked it with a different password, and used this to store my passwords. I found that something automatically puts my password for Login Passwords into Login. If Login is unlocked, and does not contain the unlock password for Login Passwords, then when I try to unlock Login Passwords, a Polkit dialog will appear, prompting me to enter the unlock password for Login Passwords. Below the text input box is text that says, “Automatically unlock this keyring whenever I’m logged in”, and a space next to it where it seems there should be a checkbox. Login will not appear to have the unlock password for Login Passwords, but if I lock and unlock Login Passwords, I am not prompted for the key, and the keyring unlocks immediately. Restarting Seahorse/Keys and Passwords shows that Login has the unlock password for Login Passwords, and while Login is unlocked, Login Passwords can be unlocked with the unlock password stored in Login. If I delete the unlock key from Login, Login Passwords will be properly locked and will prompt for its password when I try to unlock it, again with the seemingly broken Polkit dialog. What’s more, after I delete the unlock key from Login, and restart Seahorse/Keys and Passwords, Login will not appear, but Login Passwords will. How can I fix this so that the unlock password for Login Passwords is not stored in Login?