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.
After killing and restarting the keyring which fixed Network Manager, then Chromium developed a slow start problem caused by gnome-keyring.
smm@laptop ~ logging= stderr 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.
$ chromium-browser --enable-
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: