Chromium won't detect password store in simple environments

[Nathan Teodosio]

I use dwm as my window manager, which I start from console with startx; Nonetheless the Gnome Keyring running and unlocked,

% ps ax|grep [g]nome-key
   2745 ? Sl 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
   2746 ? SLsl 0:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring

With chromium password-manager-interface connected, it is expected that Chromium will use the Gnome Keyring.

In that environment, however, Chromium passwords are neither available nor saved because it fails to detect the Gnome Keyring as a password store[1]:

--->
% chromium --enable-logging=stderr --v=1 |& grep OSCrypt
[140376:140376:0313/170223.647134:VERBOSE1:key_storage_linux.cc(122)] Selected backend for OSCrypt: BASIC_TEXT
[140376:140376:0313/170223.647148:VERBOSE1:key_storage_linux.cc(142)] OSCrypt did not initialize a backend.
<---

However, if I give it a hand, it works fine:

--->
chromium --password-store=gnome --enable-logging=stderr --v=1 &> file
[141078:141078:0313/170300.130433:VERBOSE1:key_storage_linux.cc(122)] Selected backend for OSCrypt: GNOME_ANY
[141078:141078:0313/170300.260235:VERBOSE1:key_storage_linux.cc(174)] OSCrypt using Libsecret as backend.
<---

In the default Ubuntu Gnome desktop it detects the store fine.

Should we feed --password-store=gnome when the Keyring is detected to be running?

[1]: https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md