[GH-ISSUE #33] Not being able to access X server without mods #32

New issue

Closed

opened 2026-03-04 12:24:05 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 12:24:05 +03:00

Owner

Originally created by @thjwong on GitHub (Feb 1, 2021).
Original GitHub issue: https://github.com/cascadium/wsl-windows-toolbar-launcher/issues/33

All applications except the terminal applications were not able to access the X server (VcXsrv):

I have to add the following code to the .bat files before calling the wsl.exe in order to make them work:

for /f "tokens=3 delims=: " %%i in ('netsh interface ip show config name^="Wireless" ^| findstr "IP Address" ^| findstr [0-9]') do set DISPLAY=%%i:0.0

set WSLENV=DISPLAY/u

Originally created by @thjwong on GitHub (Feb 1, 2021). Original GitHub issue: https://github.com/cascadium/wsl-windows-toolbar-launcher/issues/33 All applications except the terminal applications were not able to access the X server (VcXsrv): I have to add the following code to the .bat files before calling the wsl.exe in order to make them work: > for /f "tokens=3 delims=: " %%i in ('netsh interface ip show config name^="Wireless" ^| findstr "IP Address" ^| findstr [0-9]') do set DISPLAY=%%i:0.0 > > set WSLENV=DISPLAY/u

kerem referenced this issue

2026-03-04 12:24:05 +03:00

[GH-ISSUE #32] rc_file is not respected and zsh support. #33

kerem closed this issue

2026-03-04 12:24:06 +03:00

kerem commented

2026-03-04 12:24:06 +03:00

Author

Owner

@fquinner commented on GitHub (Feb 2, 2021):

If x forwarding is not working, it's most likely a firewall or addressing issue. What you're doing there is connecting to X through your wireless interface's IP (which is likely a private network as opposed to WSL which for some random reason is registered as a "public" network and therefore has different firewall rules).

It's a common shortcut that a lot of people end up taking, but ultimately it shouldn't be required. You could also do the same thing in .bashrc if you like without having to modify the .bat files which could be a little easier to manage going forward if you really wanted to go down this road.

Setting an appropriate .bashrc and ensuring the firewall rule updates as documented here should be enough to get up and running.

@fquinner commented on GitHub (Feb 2, 2021): If x forwarding is not working, it's most likely a firewall or addressing issue. What you're doing there is connecting to X through your wireless interface's IP (which is likely a private network as opposed to WSL which for some random reason is registered as a "public" network and therefore has different firewall rules). It's a common shortcut that a lot of people end up taking, but ultimately it shouldn't be required. You could also do the same thing in .bashrc if you like without having to modify the `.bat` files which could be a little easier to manage going forward if you really wanted to go down this road. Setting an appropriate `.bashrc` and ensuring the firewall rule updates as documented [here](https://github.com/cascadium/wsl-windows-toolbar-launcher#troubleshooting) should be enough to get up and running.

No labels

duplicate

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/wsl-windows-toolbar-launcher#32

No description provided.

Rows
Columns