1. Radical: uninstall gnome-keyring or sudo mv /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon-old && sudo killall gnome-keyring-daemon
I'll rule out no 1 because some packages rely on gnome-keyring and will either fail on install or make the problem reappear.
2. provide an empty password to the keyring: https://www.ricksdailytips.com/prevent- ... th-ubuntu/
You don't bork security because of a misbehaving app.
3. edit the chromium desktop file to use basic password storage: https://ubuntuforums.org/showthread.php ... st13708937
No 2 and 3 work but are not desirable options if the user stores passwords in the browser. If we can't find another solution we should choose no 3 and investigate keepass/keepassxc.--password-store=<basic|gnome|kwallet>
Set the password store to use. The default is to automatically detect based on the desktop environment. basic selects the built in, unencrypted password store. gnome selects Gnome keyring. kwallet selects (KDE) KWallet. (Note that KWallet may not work reliably outside KDE.)
4. Setting the keyring password to the login password - that way the keyring should be unlocked during login. But for some reason on our systems gnome-keyring doesn't get auto unlocked during login.
No 4 would be the best way to go but doesn't work on our systems because we are missing integral parts of gnome that might make this work.