You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an aws ec2 instance with ssh exposed. If i ssh -X ... to it from my win11 22h2 (22624.1470) wslg kali or ubuntu terminal and then launch any x11 app it fires up on my local windows desktop.
If at the same time that i have that wslg distro terminal ssh -X ... connection active i start another ssh -X ... from my windows powershell terminal and apply export DISPLAY=localhost:10.0 after that i can also launch any x11 app from that session also and fires it up on my local windows desktop, no xserver [ vcxsrv xming ] install required.
If i disconnect the wslg distro terminal ssh -X ... connection the ability to launch any x11 app from my windows powershell terminal ssh -X ... connection stops working.
Question1 - is there a way i can manually initialize whatever wslg wayland xserver support story is being initialized when i start wslg distro terminal ssh -X ... connections so that i can just use windows powershell terminal ssh -X ... connections to reach my aws ec2 instances with x11 app support and not be required to have any wslg distro terminal ssh -X ... connection running?
Question2 - how come wsg distro terminal executed ssh -X ... connection to my aws ec2 instances automatically has DISPLAY=localhost:10.0 without me having to do anything. Is it the wslg distro terminal's ssh client that is doing that as a result of including the -X[11Forwarding] switch setting? If so does that mean the windows powershell terminal ssh client has issues since establishing ssh -X ... connection with it doesn't end up with any $DISPLAY environment variable setting in place automatically.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have an aws ec2 instance with ssh exposed. If i
ssh -X ...
to it from my win11 22h2 (22624.1470) wslg kali or ubuntu terminal and then launch any x11 app it fires up on my local windows desktop.If at the same time that i have that wslg distro terminal
ssh -X ...
connection active i start anotherssh -X ...
from my windows powershell terminal and applyexport DISPLAY=localhost:10.0
after that i can also launch any x11 app from that session also and fires it up on my local windows desktop, no xserver [ vcxsrv xming ] install required.If i disconnect the wslg distro terminal
ssh -X ...
connection the ability to launch any x11 app from my windows powershell terminalssh -X ...
connection stops working.Question1 - is there a way i can manually initialize whatever wslg wayland xserver support story is being initialized when i start wslg distro terminal
ssh -X ...
connections so that i can just use windows powershell terminalssh -X ...
connections to reach my aws ec2 instances with x11 app support and not be required to have any wslg distro terminalssh -X ...
connection running?Question2 - how come wsg distro terminal executed
ssh -X ...
connection to my aws ec2 instances automatically hasDISPLAY=localhost:10.0
without me having to do anything. Is it the wslg distro terminal's ssh client that is doing that as a result of including the -X[11Forwarding] switch setting? If so does that mean the windows powershell terminal ssh client has issues since establishingssh -X ...
connection with it doesn't end up with any $DISPLAY environment variable setting in place automatically.Beta Was this translation helpful? Give feedback.
All reactions