What can be said is: You can restore **Chromium** passwords that way, even if you delete all the keyring data.
> This means I can safely delete the hundreds of google chrome passwords stored in the gnome keyring? > (under application chrome-16295873) _That_ I wouldn't go so far as to say. Consider Electron for example that uses Chromium as an engine, who knows if one application has stored passwords under that label? Not to mention some users parallelly install Google Chrome. -- 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/1997168 Title: [snap] Passwords are saved but not loaded with gnome keyring Status in chromium-browser package in Ubuntu: Fix Released Bug description: Steps to reproduce: * System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in VirtualBox to rule out any side-effects from preexisting configurations * Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt dist-upgrade -y && sudo snap refresh` * Install chromium from snap (`sudo snap install chromium`) * Connect chromium to password manager service (`sudo snap connect chromium:password-manager-service`) -> now chromium should be able to use gnome keyring to store its master password * Launch chromium, navigate to "chrome://settings/passwords" * Add a new password ("Saved Passwords" -> "Add") * Password shows up under "Saved Passwords" as expected. * Close chromium and open it again, navigate to "chrome://settings/passwords" * Expected: Password should show up. Instead: The list is empty. * Add another password: List stays empty. What I found out so far: * Despite of the list showing up as empty in chromium, both passwords have been stored in "~/snap/chromium/common/chromium/Default/Login Data" (to confirm, grep for the username of the saved login, as the password itself will be encrypted) * It seems that the snap version of chromium does not create the entries "Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring, which seems to be necessary at the moment (see http://crbug.com/660005). If a non-snap version of chromium (e.g. from https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first, which is used to bootstrap the user's chromium config folder and which creates the aforementioned entries in the gnome keyring, things are working fine, even after transitioning to the snap version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997168/+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
