Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
Klikini opened this issue Dec 28, 2019 · 6 comments
Closed
Labels

Comments

@Klikini
Copy link

Klikini commented Dec 28, 2019

Repro steps:

  1. Select "Connect registries..."
  2. Enter username and password

Action: vscode-docker.registries.connectRegistry
Error type: Error
Error Message: The name org.freedesktop.secrets was not provided by any .service files

Version: 0.9.0
OS: linux (OpenSUSE Tumbleweed)
Product: Visual Studio Code
Product Version: 1.41.1
Language: en

@philliphoff
Copy link
Member

@Klikini Is this error repeatable (on this machine, or others)? This error can suggest that Linux credentials management components, such as gnome-keyring are not completely installed/configured/running.

@Klikini
Copy link
Author

Klikini commented Jan 7, 2020 via email

@philliphoff
Copy link
Member

The underlying problem seems to be that kwallet does not support the common API required by the Linux libsecret library, which is used by the node-keytar library on Linux as the generalized credential store. So, on KDE, gnome-keyring is still required. (This seems to have been the case for some time; see this VS Code issue for links to more discussion.)

@Klikini
Copy link
Author

Klikini commented Jan 7, 2020

Okay, I understand. I installed gnome-keyring and it works, so this is a duplicate of #205.

@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 21, 2020
@ItalyPaleAle
Copy link

Stumbled upon this ticket while researching a similar issue.

Testing VS Code on a Chromebook with Crostini, after logging into GitHub I got this error:

Screenshot 2020-11-18 at 19 19 00

Following this issue, I fixed it by installing gnome-keyring.

However, I wonder if it would make sense to add gnome-keyring as a dependency for VS Code's package?

@bwateratmsft
Copy link
Collaborator

The authentication provider API in VSCode is going to add a secret storage API, so we're planning to use that. It would hopefully fix the issue, otherwise it will at least make it external to us.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants