Hello Steve, or anyone else affected, Accepted chromium-browser into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chromium- browser/77.0.3865.120-0ubuntu1.19.10.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: chromium-browser (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- 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: Fix Committed 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
