This bug was fixed in the package chromium-browser -
77.0.3865.120-0ubuntu2
---------------
chromium-browser (77.0.3865.120-0ubuntu2) focal; urgency=medium
* debian/chromium-browser.preinst: revert a previous change which was causing
upgrades from disco to eoan to install the snap but not connect the
password-manager-service interface (LP: #1849160)
* debian/control: update Vcs-Bzr URL to point to the branch for 20.04
(codename the Focal Fossa)
-- Olivier Tilloy <[email protected]> Tue, 22 Oct 2019
16:20:34 +0200
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
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:
Fix Released
Status in chromium-browser source package in Eoan:
In Progress
Bug description:
[Impact]
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.
[Test Case]
Install chromium-browser in disco (19.04), save a few passwords for login
forms.
Dist-upgrade to eoan (19.10), launch chromium, and verify that the saved
passwords are still there. They can be inspected by browsing to
chrome://settings/passwords.
As an additional check, the output of `snap connections chromium | grep
password` should look like this:
password-manager-service chromium:password-manager-service
:password-manager-service manual
I.e. the interface should be marked as manually connected, even though
the user hasn't explicitly connected it.
[Regression Potential]
Low. The change removes an assumption on upgrade paths that has become
incorrect. Now the password-manager-service interface will always be
connected on upgrade, which I think is sensible. Users who wish to
disconnect the interface (unlikely use case) will also have to remove
the chromium-browser transitional package, to prevent it from
reconnecting the interface.
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 : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
