Vscode-remote-release: Remote WSL not working when using fish shell

[w-biggs]

• VSCode Version: 1.36.0
• Local OS Version: Windows_NT x64 10.0.18362 (Windows 10 1903)
• Remote OS Version: Ubuntu 18.04.1 LTS
• Remote Extension/Connection Type: WSL

Launching VSCode remotely results in this:

[2019-07-08 20:26:41.707] Starting VS Code Server inside WSL (Ubuntu)
[2019-07-08 20:26:41.707] Windows build: 18362. Multi distro support: enabled
[2019-07-08 20:26:41.968] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe -d Ubuntu bash -c "[ -d ~/.vscode-server/bin/0f3794b38477eea13fb47fbe15a42798e6129338 ] && echo found || echo missing"
[2019-07-08 20:26:43.862] Server install found in WSL
[2019-07-08 20:26:43.862] Launching C:\WINDOWS\System32\wsl.exe -d Ubuntu bash -c "'$(wslpath -u 'c:/Users/WB/.vscode/extensions/ms-vscode-remote.remote-wsl-0.38.8/scripts/wslServer.sh')' '0f3794b38477eea13fb47fbe15a42798e6129338' 'stable' '.vscode-server' '' 0  " in c:\Users\WB\.vscode\extensions\ms-vscode-remote.remote-wsl-0.38.8
[2019-07-08 20:26:45.735] fish: $(...) is not supported. In fish, please use '(wslpath)'.
[2019-07-08 20:26:45.735] bash -c "'$(wslpath -u 'c:/Users/WB/.vscode/extensions/ms-vscode-remote.remote-wsl-0.38.8/scripts/wslServer.sh')' '0f3794b38477eea13fb47fbe15a42798e6129338' 'stable' '.vscode-server' '' 0  "
[2019-07-08 20:26:45.735]           ^
[2019-07-08 20:26:45.736] VS Code Server for WSL closed unexpectedly.
[2019-07-08 20:26:45.736] For help with startup problems, go to
[2019-07-08 20:26:45.736] https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips

[Aulos]

Yup. I have the same issue after updating today.

[dakzilla]

Also broken with ZSH after the latest update.

Update: Changing the default shell back to Bash doesn't make a difference. Here is my error log:

[2019-07-09 13:01:33.067] Starting VS Code Server inside WSL (default distro)
[2019-07-09 13:01:33.067] Windows build: 16299. Multi distro support: enabled
[2019-07-09 13:01:33.399] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe  bash -c "[ -d ~/.vscode-server/bin/0f3794b38477eea13fb47fbe15a42798e6129338 ] && echo found || echo missing"
[2019-07-09 13:01:33.527] Server install found in WSL
[2019-07-09 13:01:33.528] Launching C:\WINDOWS\System32\wsl.exe bash -c "'$(wslpath -u 'c:/Users/<username>/.vscode/extensions/ms-vscode-remote.remote-wsl-0.38.8/scripts/wslServer.sh')' '0f3794b38477eea13fb47fbe15a42798e6129338' 'stable' '.vscode-server' '' 5000  " in c:\Users\<username>\.vscode\extensions\ms-vscode-remote.remote-wsl-0.38.8
[2019-07-09 13:01:33.697] /bin/bash: wslpath: command not found
[2019-07-09 13:01:33.697] bash: : command not found

Update 2: Fixed after reverting to Remote - WSL v0.38.7. Now, VSCode really doesn't want you using outdated extensions so here's what I did:

1. Downloaded the .VSIX for version 0.38.7 from here
2. Launch VS Code and uninstall the WSL extension
3. In the extensions menu, disable Auto-updating extensions
4. Close VS Code to free up the file handles on the extension directories. Go into your home directory/.vscode/extensions folder and delete any folder starting with "ms-vscode-remote.remote-wsl". Since you closed VS Code, the folders should not be locked. If they are, just kill the code process or reboot.
5. Launch VS Code and from the extensions menu, choose "Install from VSIX". Select the extension you downloaded earlier in your Downloads folder.
6. The extension is now installed. Test it by launching a new WSL session. Fingers crossed, the issue should be fixed until a new version of the extension is published by MS.

[harsox]

I'm getting a similar error with default bash shell

[2019-07-09 13:18:36.984] Starting VS Code Server inside WSL (default distro)
[2019-07-09 13:18:36.984] Windows build: 16299. Multi distro support: enabled
[2019-07-09 13:18:37.691] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe  bash -c "[ -d ~/.vscode-server-insiders/bin/9296aaa2201b638e2b1dc71a9b9fe38c5ab2e904 ] && echo found || echo missing"
[2019-07-09 13:18:37.924] No server install found on WSL, downloading server on client side...
[2019-07-09 13:18:37.955] Unable to detect if server is already installed: Error: getaddrinfo ENOTFOUND update.code.visualstudio.com update.code.visualstudio.com:443
[2019-07-09 13:18:37.955] Launching C:\WINDOWS\System32\wsl.exe bash -c "'$(wslpath -u 'c:/Users/____/.vscode-insiders/extensions/ms-vscode-remote.remote-wsl-0.38.8/scripts/wslServer.sh')' '9296aaa2201b638e2b1dc71a9b9fe38c5ab2e904' 'insider' '.vscode-server-insiders' '' 0  " in c:\Users\____\.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.38.8
[2019-07-09 13:18:38.289] /bin/bash: wslpath: command not found
[2019-07-09 13:18:38.289] bash: : command not found

[w-biggs]

Just got an update today to version 2213894ea0415ee8c85c5eea0d0ff81ecc191529 but it's still occurring for me.

[johnsonwj]

Also happening on build 17763

[2019-07-09 21:21:57.303] Starting VS Code Server inside WSL (default distro)
[2019-07-09 21:21:57.303] Windows build: 17763. Multi distro support: enabled
[2019-07-09 21:21:57.537] Launching C:\WINDOWS\System32\wsl.exe bash -c "'$(wslpath -u 'c:/Users/johns/.vscode-insiders/extensions/ms-vscode-remote.remote-wsl-0.38.8/scripts/wslServer.sh')' '9296aaa2201b638e2b1dc71a9b9fe38c5ab2e904' 'insider' '.vscode-server-insiders' 'C:/Users/johns/AppData/Local/Temp/vscode-remote-wsl/9296aaa2201b638e2b1dc71a9b9fe38c5ab2e904/vscode-server-linux-x64.tar.gz' 0  " in c:\Users\johns\.vscode-insiders\extensions\ms-vscode-remote.remote-wsl-0.38.8
[2019-07-09 21:21:57.729] fish: $(...) is not supported. In fish, please use '(wslpath)'.
[2019-07-09 21:21:57.729] bash -c "'$(wslpath -u 'c:/Users/johns/.vscode-insiders/extensions/ms-vscode-remote.remote-wsl-0.38.8/scripts/wslServer.sh')' '9296aaa2201b638e2b1dc71a9b9fe38c5ab2e904' 'insider' '.vscode-server-insiders' 'C:/Users/johns/AppData/Local/Temp/vscode-remote-wsl/9296aaa2201b638e2b1dc71a9b9fe38c5ab2e904/vscode-server-linux-x64.tar.gz' 0  "
[2019-07-09 21:21:57.729]           ^
[2019-07-09 21:21:57.729] VS Code Server for WSL closed unexpectedly.
[2019-07-09 21:21:57.729] For help with startup problems, go to
[2019-07-09 21:21:57.729] https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips

Edit: adding info from About screen

Version: 1.37.0-insider (user setup)
Commit: 9296aaa2201b638e2b1dc71a9b9fe38c5ab2e904
Date: 2019-07-09T05:26:27.407Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17763

[johnsonwj]

I downgraded to Remote - WSL extension version 0.38.7 and it works again!

Edit - derp this was already mentioned above :P

[w-biggs]

This is still occurring with the latest 0.38.9 for me. Downgrading to 0.38.7 works fine, though.

[wight554]

0.38.10 fixed the issue but opens bash by default
fastest solution I've found to far is to exec fish in _.bashrc_

[dakzilla]

I also confirm that 0.38.10 fixed the issues introduced in 0.38.8. On my setup (Windows build 16299 + Ubuntu1804 + ZSH) the WSL session starts correctly and the correct shell is used.

[w-biggs]

0.38.10 is sorta working but it's opening bash by default for me as well.

Edit: Should I make a new issue for this? Or edit this issue? Not sure what the best thing to do is.

[Aulos]

It works for me. Have you used chsh?

pt., 12 lip 2019, 22:13 użytkownik W Biggs [e-mail]
napisał:

0.38.10 is sorta working but it's opening bash by default for me as well.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-remote-release/issues/934?email_source=notifications&email_token=AADNTIYZC4RHQV5YYMRVFVTP7DQXVA5CNFSM4H67GZLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ2YO4A#issuecomment-511018864,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADNTI4CND3Y3WOKFGU7GSLP7DQXVANCNFSM4H67GZLA
.

[w-biggs]

It works for me. Have you used chsh?

I actually just did "select default shell" from the dropdown and that worked. Odd that it didn't pick that up immediately like it used to but now it's working fine. Thanks. Closing since I guess it's totally fixed?