-
Notifications
You must be signed in to change notification settings - Fork 311
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
X11 Forwarding with Remote-ssh #10657
Comments
I guess the primary ask is for X11 to work through remote-ssh and forwarded through to XLaunch/Xming. Is there another approach or something else I need to do to get X11 working through Remote-SSH? |
Appending to my previous. Bug #589 mentions that it's added to the extension and should just work. |
Dapatkan Outlook untuk Android<https://aka.ms/AAb9ysg>
…________________________________
From: Josh Spicer ***@***.***>
Sent: Friday, January 24, 2025 4:53:22 AM
To: microsoft/vscode-remote-release ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [microsoft/vscode-remote-release] X11 Forwarding with Remote-ssh (Issue #10657)
Thanks for the detailed issue. Is the primary ask here to set the DISPLAY variable?
Have you tried the terminal.integrated.env.linux. Adding that setting is an easy way to set environment variables in the remote terminal. You'll likely also need those X11 configuration changes
image.png (view on web)<https://github.com/user-attachments/assets/d5327c9a-aa01-4809-a888-fd611d35fede>
Please let me know if this helps
—
Reply to this email directly, view it on GitHub<#10657 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BESOU5L7MJKKYLBBNZDMDVD2MFQFFAVCNFSM6AAAAABVYCSQZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJRGA4TGMZTHA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Maybe "Remote-SSH: Kill Current VS Code Server", followed by "Reload Window" would fix it. That's the only reliable way for me to update SSH_AUTH_SOCK environment variable in the terminal, to get Agent Forwading working. Maybe the same thing applies to your DISPLAY environment variable. |
Thank you for your reply. Agent Forwarding works for me. |
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
setting[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
Some of the details are redacted.
Remote-SSH Log
Expected Behavior
I currently ssh using the SSH_AUTH_SOCK variable to pipe PIV card information through pageant using the wsl-ssh-pageant tool.
This ssh goes through a bastion and then connects to the server I want to. I've followed suggestions mentioned in issue [#267] and [#589]. I set the Display variable in windows to localhost:0.0 hoping the remote-ssh extension would pick that up and pass it on through to enable x11 through the terminal
Actual Behavior
Remote-ssh never seems to actually set the DISPLAY variable in the bash terminal (of the remote server). I can get x11 to work if I first start a putty session, get the display variable from putty and manually set that in the bash terminal. But it doesnt do it manually and connect with Xming.
Steps To Reproduce
This is my config file. I've tried both
ssh -X
andssh -Y
along with turning on bothForwardX11
andForwardX11Trusted
. Ive also tried setting a remotecommand also to no avail.Anything else?
Ive also tried using the Remote-X11 extension (didnt work) but Id like to ideally get it working with remote-ssh
The text was updated successfully, but these errors were encountered: