I use KeePass 2 on Mono so I'm not too bothered by this. Wifi and NetworkManager still have problems though.
On Google Chrome and likely Chromium I fixed the 2 minute start wait by adding --password-store=basic the command line. You can add it the Exec entry in your desktop file or by editing the menu entry with menu-libre or equivalent. You will have to sign in to Chrome again if you use their syncing functionality. I like syncing because I can see history and open tabs from my phone on my desktop and vice versa. It seems Chromium uses a plain text password store with the basic option so you may not prefer this option. I don't use Chromium password storage since I use KeePass so it works for me. https://chromium.googlesource.com/chromium/src/+/lkcr/docs/linux_password_storage.md I have read that PAM is supposed to unlock the keyring as configured in LightDM (My current display manager) but that's not being done apparently. There is alot of garbage on Google about incompatibilities with autologin. My account is not set to autologin and requires a password to login. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
