Vscode-remote-release: Code-insiders started from WSL doesn't return to console/ doesn't connect

Created on 23 Jun 2019  路  5Comments  路  Source: microsoft/vscode-remote-release

Intro:

  • I've searched and found 2 similar problems, but no solution reported there works for me and, even when following the guidance, my issue remains. See 46462 and 44540
  • I've installed the latest code-insiders release
  • VSCode Version: 1.36.0-insider (user setup)
  • OS Version: Windows 10 with latest patches

Steps to Reproduce:

  1. Install Code-Insiders
  2. Open WSL
  3. type code-insiders .
  4. a: Code insiders opens up in Windows, does not connect to WSL
  5. b: WSL shows log output from code-insiders, e.g.:
[main 2019-06-23T15:41:16.497Z] update#setState idle
[main 2019-06-23T15:41:46.501Z] update#setState checking for updates
[main 2019-06-23T15:42:02.481Z] update#setState idle
  • same result when launching with code-insiders . --disable-extensions, launching with code . opens up regular vs code (doesn't leak, but also has no native WSL support). So, does this issue occur when all extensions are disabled? Yes!

My Path environment variables for code and code-insiders:

which code-insiders
/c/Users/[me]/AppData/Local/Programs/Microsoft VS Code Insiders/bin/code-insiders
which code
/c/Program Files/Microsoft VS Code/bin/code

My WSL is based on the official Ubuntu 18.04, setup with LxRunOffline

  • starting code-insiders with code-insiders . from WSL worked until the last week. So this issue didn't occur before the latest version of code-insiders.
bug verified wsl

All 5 comments

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

Thanks @vscodebot, these issues do not seem to be related to my bug described above.

@Sieboldianus I believe I have the same issue you are describing.

The error has been fixed with the latest update. Thank you!

Just tested, it works! Many thanks!

Was this page helpful?
0 / 5 - 0 ratings