No, it's not connected. There have been similar reports, and I think I
understand what's going on.
I will SRU a fix to the chromium-browser package. In the meantime, I suggest
you run:
snap connect chromium:password-manager-service
(please confirm whether this fixes the problem)
--
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/1849160
Title:
after deb->snap transition, chromium no longer sees local password
store
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
After upgrading to eoan and accepting the deb->snap transition for
chromium, the passwords saved in my browser are no longer available to
the app, despite
~/snap/chromium/current/.config/chromium/Default/Login Data being
present and fully-populated. If I go into settings, I see Saved
Passwords: Saved passwords will appear here.
The data doesn't appear to be lost, since I have a copy in ~/snap as
well as in ~/.config/chromium, but somehow they're inaccessible.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
