-
Notifications
You must be signed in to change notification settings - Fork 821
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
Unable to run exe from Gnome-Terminal #4148
Comments
I think I have found the reason. Different session gives different WSL_INTEROP, and those in Gnone-Terminal or some other gui terminal apps doesn't work. If I export WSL_INTEROP in wsl started from cmd to Gnome-Terminal, everything works fine. If I do the opposite way, both will stop calling exe programs |
Actually if I start Gnome-terminal with |
Found a solution:
to ~/.bash_profile |
Hi @karuboniru it seems like you have a solution to your issue! Thank you for your detective work, if everything is working please close out the issue. :) |
@karuboniru - I wouldn't suggest that solution. I am working on a fix for this. |
Yes. My code "stole" a WSL_INTEROP socket randomly from Maybe you can provide a persisting socket in next releases? |
I experience similar problem in TMUX but not outside it.
I have several |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Your Windows build number:
18197.1000
What you're doing and what's happening:
When In Gnome-terminal (tilix had the same problem)
[yan@BOOK-Karuboniru ~]$ ipconfig.exe
<3>init: (217) ERROR: UtilConnectToInteropServer:270: connect failed 2
[yan@BOOK-Karuboniru ~]$
When In CMD.exe ----> run wsl.exe--->run something else
I can call exe programs normally
What's wrong / what should be happening instead:
I didn't test if it behaves the same in WSL1. I am using WSL 2
Calling exe should work fine even in Linux Terminal apps
log.zip
The text was updated successfully, but these errors were encountered: