[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
I'm trying to understand why the user is enforced to do action described in
file:///snap/chromium/2381/firstrun/password-en.html
manually instead of the package manager which introduced the change ?
And if the user is required to take manual action, the message which is
slightly modified version of post #9 above needs to be more precise. Especially
if with or without this manual action any password migration/reencryption
happened or will happen and how it's exactly done. Also besides 'Login Data' in
my case there are few more:
'Login Data-journal' - empty - probably SQlite which could be ignored
'Login Data 2-journal' - also empty but here I'm not sure
'Login Data For Account' - not empty, almost the size of 'Login Data'
'Login Data For Account-journal' - empty
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
This means I can safely delete the hundreds of google chrome passwords stored
in the gnome keyring?
(under application chrome-16295873)
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
The passwords are always in "Login Data" (hereby LD) file and remain in
that file.
If the password-manager-service interface (as displayed by 'snap
connnections chromium') is
- connected, then --password-store=gnome and the passwords in Chromium
(stored in LD) are encrypted with a key stored in the Gnome Keyring
under the name of Chromium Safe Storage or something like that.
- not connected, then --password-store=basic and the passwords in
Chromium (stored in LD) are not encrypted and thus independent of the
Gnome Keyring.
If you want to be overly cautious before committing to any action, you
can always retrieve a CSV of your passwords by entering
about:settings/passwords in the address bar, then in the _Saved
Passwords_ section click the 3 dots and _Export passwords_. That CSV can
then be imported back in case something goes awry.
On 28/02/2023 13:26, Martin wrote:
> Will my passwords then migrate from "Login Data" to the Gnome Wallet? I
> have chrome passwords in "Login Data" and in the Gnome Wallet (Keyring)
> and it is not clear what is the main password source. Even if using "--
> password-store=gnome".
>
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
Will my passwords then migrate from "Login Data" to the Gnome Wallet? I
have chrome passwords in "Login Data" and in the Gnome Wallet (Keyring)
and it is not clear what is the main password source. Even if using "--
password-store=gnome".
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
Martin, if you rename 'Login Data' -> 'Login Data.old' (or whatever
other name), then your passwords will be saved in 'Login Data.old'.
Chromium will not use that file, it only recognizes 'Login Data', so you
will not be able to access the passwords from Chromium until you rename
it back to 'Login Data'.
If everything is working fine as far as you are concerned, you can just
create an empty 'Login Data.old' to get rid of the message.
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
If I rename "Login Data", I will lose all my passwords in "Login Data"?!
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
** 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/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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
This fix is now released to the edge channel of the official snap. Since
it requires moving private data file out of the way (as in step 2 of #3,
but a single file instead of a whole directory) so that another good one
can replace it, it includes directions for the user to do it himself.
--
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 Committed
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
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 Committed
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
I tested it with a fresh install of Ubuntu and I can confirm that the
fix is working!
Thanks for fixing this so quickly :-)
--
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:
In Progress
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
I released the (possible) fix in stable/password branch. You can install
it with
snap install --channel stable/password chromium
Please make sure to connect the interface as in the bug description,
snap connect chromium:password-manager-service
It might also be a good idea to delete the Chromium entries from
Seahorse before the test.
--
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:
In Progress
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
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:
In Progress
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
** Tags added: password-storage
--
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:
Triaged
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
Reproduced in Kinetic virtual machine.
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
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:
Triaged
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
Thank you for the bug report.
Hmm I see you are testing in a pretty clean environment, but it works
fine for me on stable (107.0.5304.110), the list is not empty.
I verified I had "Chrome Safe Storage" and "Chrome Safe Storage Control"
in the gnome keyring, I deleted them and Chromium's settings directory,
tried again and it worked as well, confirming that those two entries
were not generated in the keyring.
I'll try it in a clean environment and let you know.
--
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:
New
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
