microsoft / microsoft/vscode-remote-release

ENV cannot take effect

Open
#10,614 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ssh
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Is there an existing issue for this bug?
  • I have searched the existing open issues and found none that apply.
  • If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
  • I have read and performed the troubleshooting steps
  • I have tried both values of the remote.SSH.useLocalServer setting
  • My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
  • I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot

I did not ask the @remote-ssh participant for help

In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?

I did not try step 2 of the troubleshooting steps

Remote-SSH Log

I have add setting to my remote config-folder .vscode/setting.json

    "terminal.integrated.env.linux": {
        "DISPLAY":"acker.xxxxxx.xin:0"
    },

and i open the bash, echo $DISPLAY, it still be :0

Expected Behavior

acker.xxxxxx.xin:0

Actual Behavior

0

Steps To Reproduce

also , i set this config to my local vscode setting.
i get the same result

Anything else?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported terminal.integrated.env.linux setting in the remote .vscode/settings.json and compare it with the same setting in local VS Code settings. Reproduce the Remote-SSH session, inspect the Remote-SSH: Show Log output, and verify whether the configured DISPLAY value reaches the bash environment instead of :0.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, vscode
Domain
developer-experience, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.