After killing and restarting the keyring which fixed Network Manager, then Chromium developed a slow start problem caused by gnome-keyring.
smm@laptop ~ $ chromium-browser --enable-logging=stderr ATTENTION: default value of option force_s3tc_enable overridden by environment. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [7981:7981:0314/102437.107901:WARNING:password_store_factory.cc(241)] Using basic (unencrypted) store for password storage. See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_password_storage.md for more information about password storage options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
