4

Arch's docs on Chromium Browser say that for the purposes of storing passwords it uses either

  • gnome, uses Gnome Keyring
  • kwallet5, uses KDE Wallet
  • basic, saves the passwords and the cookies' encryption key as plain text in the file Login Data
  • detect, the default auto-detect behavior

Is there anyway to find out which one it is using. I know Chrome is configured in many places, like /etc/default/google-chrome and in many other places for the user, system, and session. How do I know which Password Store Crhomium is using?

Improve this question

1 Answer 1

Reset to default
2

I found running it with the verbose flag gave me what I was looking for, chromium-browser --verbose

[VERBOSE1:key_storage_util_linux.cc(53)] Password storage detected desktop environment: XFCE
[VERBOSE1:password_store_factory.cc(235)] Trying libsecret for password storage.
[VERBOSE1:key_storage_linux.cc(61)] OSCrypt using Libsecret as backend.
[VERBOSE1:password_store_factory.cc(238)] Using libsecret keyring for password storage.

I was able to get my browser to work under a different window manager by force providing --password_store=gnome

Improve this answer
6
  • It is --password-store=gnome. I tried it, but only the first one of those lines did not appear. I am using Xubuntu 18.04.
    – jarno
    Commented Sep 22, 2019 at 10:08
  • Besides, storing passwords still changes '~/.config/chromium/Default/Login Data'.
    – jarno
    Commented Sep 22, 2019 at 12:25
  • Even if gnome-keyring-daemon is running.
    – jarno
    Commented Sep 22, 2019 at 12:30
  • libsecret may communicate with gnome-keyring-daemon.
    – jarno
    Commented Sep 22, 2019 at 13:24
  • Currently the correct flags are --enable-logging=stderr --v=1. 1 2
    – Will Chen
    Commented Nov 21, 2022 at 18:13

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .