can't log in: The name org.freedesktop.secrets was not provided by any .service files

[obedm503]

Description

just installed the .deb version from https://github.com/shiftkey/desktop/releases/tag/release-1.0.11 it installed fine but fails to log in to my github account consistently, and shows the error

then I tried the "Sign in using you browser" but that also fails and shows

Version

GitHub Desktop version: 1.0.11

OS version:

Steps to Reproduce

1. install
2. try to login
3. fail to login

Expected behavior: log in somehow
Actual behavior: doesn't log in

Reproduces how often: 100%

Logs

couldn't find logs in ~/GitHub Desktop which is where I expected them to be. so these are the logs in the devtools

and judging from the network tab, it seems i was successfully authenticated by the server

Additional Information

if there more information needed about the environment feel free to let me know

[shiftkey]

@obedm503 thanks for the details!

My initial gut feeling on this is that the login flow where you provide username/password/2fa is failing when we try and add credentials to the OS credential store. We're using node-keytar which then uses libsecret which should work with both GNOME and KDE services for storing secrets, but maybe I'm missing something.

Using the browser to login is probably the same as #10, which is an Electron limitation that was fixed recently. Even if that was working, you'll probably still face the above issue because we need somewhere to store stuff.

[shiftkey]

Found this extra context for the first error:

keytar uses libsecret, which is a frontend to gnome-keyring. KWallet does not support org.freedesktop.secrets
just installed the package gnome-keyring and everything workes fine

I'm not sure how feasible that is for your use case, but I also don't have enough familiarity with whether there's an alternative to gnome-keyring that's more suitable (KWallet/KSecretService support seems to be an ongoing discussion).

[obedm503]

so if I install gnome-keyring it should work?

[shiftkey]

@obedm503 I believe so

[shiftkey]

If this can be of some help, in VS Code KWalet is used without problems.

@Bleser92 if you can find out which Node library they're using (and how they're using it) I'm happy to figure out if this can be applied to keytar in some way.

EDIT: I see VSCode is up to 4.0.5 of keytar, which is not far ahead of Desktop which is using 4.0.4 currently.

[mathetes87]

I'm also using KDE Neon and installing gnome-keyring solved the login problem for me!

[sl1pkn07]

any other alternative? i don't what install gnome-keyring because my system is crafted for gnome-free

is possible use kwallet instead?

[shiftkey]

is possible use kwallet instead?

Not currently - someone needs to contribute support for KWallet to node-keytar as well as the ability to detect and choose the right backend.

This is the issue discussing that change: atom/node-keytar#17

EDIT: node-keytar actually uses libsecret which is intended to be agnostic of the desktop you use, but KWallet doesn't implement support for it. This is the discussion you want to follow along with.

[shiftkey]

I'm going to close this out because this is outside the scope of GitHub Desktop. I'd recommend looking for alternatives to KWallet for KDE systems, but I don't seem to be able to find any based on a quick google search.

[obedm503]

After almost a year, I decided to replace KWallet with Gnome's Seahorse. It now lets me login.