Comment 5 for bug 2011281

On Mon, Mar 20, 2023 at 11:00:12AM -0000, Nathan Teodosio wrote:
> However, I just tested in my simplified dwm environment and I can
> confirm that, although the keyring is running and unlocked, the
> passwords aren't displayed in Chromium, but they are there in `Login
> Data`. So Chromium has been failing to detect[1] that Gnome keyring is
> available.

> When you observed that behavior, were you perchance in such a minimal
> environment — for which I filed LP: 2011474 —, or were you on default
> Ubuntu?

This is a default Ubuntu environment.

> Also you can verify whether or not Chromium is detecting that the Gnome
> Keyring is available by enabling logging and grepping for OSCrypt. E.g.:

> --->
> % chromium --password-store= --enable-logging=stderr --v=1 |& grep 'backend for OSCrypt'
> [...] Selected backend for OSCrypt: BASIC_TEXT
> % chromium --password-store=gnome --enable-logging=stderr --v=1 |& grep 'backend for OSCrypt'
> [...] Selected backend for OSCrypt: GNOME_ANY
> <---

Output here is:

$ chromium --password-store= --enable-logging=stderr --v=1 |& grep 'backend for OSCrypt'
[4103636:4103636:0519/230949.699268:VERBOSE1:key_storage_linux.cc(122)] Selected backend for OSCrypt: GNOME_ANY
$

chromium continues to be able to *use* my saved passwords. But I don't know
where they're actually saved, and I can't access the plain text of the
passwords through chromium, which continues to be a problem.