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

Error: Cannot autolaunch D-Bus without X11 $DISPLAY when using VisualStudioCodeCredential on Linux Codespace #21542

Closed
joshspicer opened this issue Apr 21, 2022 · 2 comments
Assignees
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-author-feedback More information is needed from author to address the issue.

Comments

@joshspicer
Copy link

Hello! I am trying to use the VisualStudioCodeCredential helper to create a credential in VSCode (connected through a linux (debian) GitHub Codespace).

Repro

  1. Connect to a Codespace through the VsCode Client.

  2. Attempt to getToken via the VisualStudioCodeCredential.

	const keyvaultUrl = getEnv('KEYVAULT_URL');

        useIdentityPlugin(vsCodePlugin);
	const credential = new VisualStudioCodeCredential();

	console.log('TOKEN', (await credential.getToken('https://vault.azure.net/.default')
                                        .catch((e) =>
		                            console.log('ERROR!!!!', e)
	)));
  1. getToken fails with Error: Cannot autolaunch D-Bus without X11 $DISPLAY.
@ghost ghost added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Apr 21, 2022
@azure-sdk azure-sdk added Azure.Identity Client This issue points to a problem in the data-plane of the library. needs-team-triage This issue needs the team to triage. labels Apr 21, 2022
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Apr 21, 2022
@sadasant sadasant self-assigned this Apr 22, 2022
@sadasant
Copy link
Contributor

Hello @joshspicer !

It seems to me that an important part of the premise of the issue you’re brining to us is whether @azure/identity-vscode should work in Codespaces or not. At the moment, @azure/identity-vscode does not work in Codespaces. The first action item for me is to make this clear on the README of @azure/identity-vscode.

Now, why are we seeing this error?

@azure/identity-vscode relies on keytar to work. This D-Bus issue seems to be a relatively common issue with keytar, see 292, 433, 224, 9262, 132.

In summary, Keytar relies on secret readers like gnome-keyring, which are not installed on Codespaces by default.

The best we can do is to improve the error message we provide. However, at the moment it is not clear to me what kind of guidance we should show, since the solution varies. One approach I’m seeing requires users to start the gnome-keyring-deamon. Give us some time to discuss and agree on what message we can provide.

@sadasant sadasant added this to the Backlog milestone Apr 26, 2022
@sadasant sadasant removed their assignment May 9, 2022
@KarishmaGhiya KarishmaGhiya added the needs-author-feedback More information is needed from author to address the issue. label May 24, 2022
@ghost ghost removed the needs-team-triage This issue needs the team to triage. label May 24, 2022
@KarishmaGhiya KarishmaGhiya added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label May 24, 2022
@ghost ghost added the no-recent-activity There has been no recent activity on this issue. label May 31, 2022
@ghost
Copy link

ghost commented May 31, 2022

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

@ghost ghost closed this as completed Jun 15, 2022
@xirzec xirzec removed this from the Backlog milestone Nov 1, 2022
@ghost ghost removed the no-recent-activity There has been no recent activity on this issue. label Nov 1, 2022
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-js that referenced this issue Dec 14, 2022
Release securityinsights microsoft.security insights 2022 12 01 preview resolved (Azure#21853)

* Adds base for updating Microsoft.SecurityInsights from version preview/2022-11-01-preview to version 2022-12-01-preview

* Updates readme

* Updates API version in new specs and examples

* Resolve merge conflicts in 2022-12-01-preview (Azure#21772)

* Adds base for updating Microsoft.SecurityInsights from version preview/2022-11-01-preview to version 2022-12-01-preview

* Updates readme

* Updates API version in new specs and examples

* Add tasks API to incidents and tasks action to automationRules (Azure#21542)

* Use generated incidents swagger instead of manual

* try to fix prettier

* try to fix prettier

* try to fix prettier

* fix example casing

* fix example casing

* fix example path and body

* fix alignment with previous swagger

* Add tasks to incidents API

* add task action to automationrules API

* prettier

* fix lint - missing workspaceName pattern

* fix lint - missing workspaceName pattern

* Update entity additional properties to match new oav example validation

* Delete redundant examples

Co-authored-by: ityankel <47292630+ityankel@users.noreply.github.com>

* Fix model and spell validations (Azure#21857)

* Fix model validation

* Add Ueba to custom-words

Co-authored-by: Anat Gilenson <53407600+anat-gilenson@users.noreply.github.com>
Co-authored-by: ityankel <47292630+ityankel@users.noreply.github.com>
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-author-feedback More information is needed from author to address the issue.
Projects
None yet
Development

No branches or pull requests

5 participants