"The name org.freedesktop.secrets was not provided by any .service files"

[ghost]

I did some googling and found that if you install gnome keyring this issue is fixed. However, I'm using KDE and its own keyring manager (Kde Wallet). Any way to get this app working with that instead?

[joshirio]

I'm interested in this as well.

'node-keytar' uses libsecret so it should work with any keychain service implementing the API.

Some links:
atom/node-keytar#17
shiftkey/desktop#7

Looks like KWallet doesn't implement this API, not sure what the progress is, did not find much info.

As a workaround I did enable pam unlocking of the gnome-keyring in sddm, it doesn't work sometimes though (randomly).

[vladimiry]

I remember I faced the same issue running e2e tests on Travis CI. To make it work there I added into the .travis.yml gnome-keyring package and below lines to execute:

      eval $(dbus-launch --sh-syntax);
      eval $(echo -n "" | /usr/bin/gnome-keyring-daemon --login);
      eval $(/usr/bin/gnome-keyring-daemon --components=secrets --start);
      /usr/bin/python -c "import gnomekeyring;gnomekeyring.create_sync('login', '');";

As far as I know, there is no known solution for how to make keytar work without gnome-keyring. I'm closing this issue since node-keytar tracker has got already relevant issue opened, I just subscribed to it.

[brenthuisman]

Pending this fix in ksecretsservice, what is the recommended way to use this application on KDE?

[vladimiry]

@brenthuisman pre 2.3.2 build is going to work regardless of keytar support. See details here #57 (comment). 2.3.2 will be released later this week.