Thanks for the report Russ.
Can you please share the output of the following command?
snap connections chromium | grep password-manager-service
I suspect the password-manager-service interface is not connected, which
would explain why it's using the basic, unencrypted password store. In
that case you can connect it like this:
snap connect chromium:password-manager-service
Please note that this is not a regression as far as the snap is
concerned, the password-manager-service interface has never been auto-
connected.
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1832786
Title:
[snap] chromium-browser ignores system password store
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
The new chromium 75 snap package intentionally ignores the system
password store:
https://chromium.googlesource.com/chromium/src.git/+/master/docs/linux_password_storage.md
Normally, chromium auto-detects what type of password store to use,
previously this has resulted in chromium connecting to the gnome
password store. The new snap release passes the command line argument:
'--password-store=basic'
Which bypasses the gnome password storage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832786/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
