Resolve shell environment failed on 1.62.1 #136791

briankintz · 2021-11-09T21:27:58Z

The shell environment no longer resolves correctly in remote terminals in 1.62.1.

A possible workaround is to manually source the shell env in remote terminals

source ~/.bashrc

Another workaround is to downgrade to `1.62.0`

configure "update.mode": "none" and install 1.62.0:
win x64: win32-x64-user | win32-x64 | win32-x64-archive
win ia32: win32-user | win32 | win32-archive
win arm64: win32-arm64-user | win32-arm64 | win32-arm64-archive
macOS: macOS x64 | macOS arm64 | macOS Universal
Linux 64: linux-x64 | linux-deb-x64 | linux-rpm-x64 | linux-snap-x64

VS Code Version: 1.62.1
OS Version: Windows 10 21H1 / WSL2 / Ubuntu 20.10

After updating from 1.62.0 to 1.62.1, the full shell environment under WSL2 isn't loaded.

Aliases from .bashrc work normally
Additional configuration files like .profile are not loaded

The remote server log shows the following errors:

[2021-11-09 22:18:30.906] [remoteagent] [error] ptyHost was unable to resolve shell environment {}
[2021-11-09 22:18:31.090] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}

Rolling back to 1.62.0 solves the problem

The text was updated successfully, but these errors were encountered:

sroby · 2021-11-09T21:56:08Z

I am having what appears to be the same issue with a SSH Remote workspace on the latest release. My .bashrc is sourced, but my .bash_profile no longer is. It seems the terminal no longer inherits the environment.

Before updating VS Code today, I have never had this problem. (Is there any easy way to temporarily downgrade VS Code (on Windows), btw?)

briankintz · 2021-11-09T22:19:47Z

Before updating VS Code today, I have never had this problem. (Is there any easy way to temporarily downgrade VS Code (on Windows), btw?)

Pick your desired OS variant from the updates page
Copy the download link
Paste into address bar and replace 1.62.1 with 1.62.0
Press enter to download

For the Windows user installer it would be:

https://update.code.visualstudio.com/1.62.0/win32-x64-user/stable

Taskle · 2021-11-09T23:46:36Z

WSL2 Ubuntu seems to be having some severe regressions with the release of v1.62.1 - I just filed #136809 and I see that #136799 is also WSL2 ubuntu-related - each seems to be issues related to SSH/connections via either the terminal or otherwise.

Hopeful someone at Microsoft can take a look soon! :)

ghost · 2021-11-10T03:14:29Z

I am having what appears to be the same issue with a SSH Remote workspace on the latest release. My .bashrc is sourced, but my .bash_profile no longer is. It seems the terminal no longer inherits the environment.

I am having the same issue with SSH Remote workspace after updating VS Code to 1.62.1

chrmarti · 2021-11-10T07:20:56Z

@alexdima This looks like a regression from the 1.62.1 fix. /fyi @aeschli

Likely duplicates: #136814, #136809, #136799, microsoft/vscode-remote-release#5844

chrmarti · 2021-11-10T09:52:30Z

@deepak1556 Identified the fix in main: e08e4d3#diff-ba73d13771267ed61274b4094ee466e9ee2256307ae6cae5ef1161d0bfaebe67

Labelling as candidate for visibility.

alexr00 · 2021-11-10T10:22:36Z

Also impacting tasks in WSL: #136799

jefferai · 2021-11-10T13:39:25Z

Chiming in: took me a while to figure out why my Go setup that has been working for years suddenly wasn't working, and it's this bug; pathing sourced from .profile was no longer working. Rolling back to 1.62.0 fixed my issues.

sroby · 2021-11-10T15:53:43Z

@briankintz: Worked great, thank you!

And this indeed confirms that 1.62.1 was the culprit in my case. (SSH, not WSL)

deepak1556 · 2021-11-10T16:39:04Z

Fixed in #136877

richtera · 2021-11-10T16:41:12Z

When will this go live? I had to restore 1.60 on my machine after messing around with shell setup for a long while.

richtera · 2021-11-10T16:44:20Z

That actually worked before. The problem I had was that clicking on a launch item that used npm, then that shell was not a login shell and it was trying to find npm on the windows side.

deepak1556 · 2021-11-10T16:45:24Z

@richtera can you check if the issue is present in latest insiders https://code.visualstudio.com/insiders which already contains the fix.

richtera · 2021-11-10T16:48:33Z

@deepak1556 Ok that works. I guess both shell problems are related. Thank you.

deepak1556 · 2021-11-10T16:50:58Z

yup thanks for testing!

briankintz · 2021-11-10T16:51:34Z

Confirmed my problems both with the shell and with tasks are fixed in the latest insiders build. Thanks @deepak1556!

taikulawo · 2021-11-11T02:38:15Z

I guess this is the same problem #136838

arobertn · 2021-11-11T13:23:55Z

Argh, first time I needed to use a remote env in months and wouldn't you know it I hit this release. And the fix is coming out today even, but in a timezone after my workday is up!

Stanzilla · 2021-11-13T02:09:38Z

What's the correct way to start a VSCode WSL instance that inherits the profile? Sometimes when I just call wsl.exe code . it does not inherit it.

aeschli · 2021-11-15T11:43:19Z

@Stanzilla It should. Check out the WSL log for the entry Using shell environment from invoking shell. Setting "remote.WSL.debug": true will give more information about the env variables that are read and set.
Please file a new issue if it doesn't work.

richtera · 2021-11-15T15:12:26Z

A lot of time I have to remove the code that distinguishes login and non-login shells in bashrc, otherwise some things like nvm, conda and so on won't get initialized. I think it might be worth it to review which parts of the system pass --login to bash or zsh during startup of Visual Studio Code.

richtera · 2021-11-16T16:03:24Z

Hmmm, I am seeing this failing again in 1.62.2. My launch.json file no longer works, although everywhere else in terminal and javascript debugging terminal the environment is correct. It looks like the current version no longer opens up the terminal first so I can't see what's happening. I will enable remote.WSL.debug to see if that helps.

richtera · 2021-11-16T16:07:41Z

Using remote.WSL.debug now shows (edited to show the whole log, it's not so large)

[2021-11-16 08:20:49.486] [remoteagent] [info] 

*
* Visual Studio Code Server
*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license https://aka.ms/vscode-remote/license
*


[2021-11-16 08:20:49.486] [remoteagent] [info] Extension host agent started.
[2021-11-16 08:20:49.693] [remoteagent] [info] Deleted from disk ms-azuretools.vscode-docker /home/andy/.vscode-server/extensions/ms-azuretools.vscode-docker-1.17.0
[2021-11-16 08:20:49.965] [remoteagent] [info] [::ffff:172.24.192.1][1419c1fa][ManagementConnection] New connection established.
[2021-11-16 08:20:49.966] [remoteagent] [info] [::ffff:172.24.192.1][427f594b][ExtensionHostConnection] New connection established.
[2021-11-16 08:20:59.478] [remoteagent] [error] ptyHost was unable to resolve shell environment {}
[2021-11-16 08:20:59.479] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 08:20:59.500] [remoteagent] [info] [::ffff:172.24.192.1][427f594b][ExtensionHostConnection] <332> Launched Extension Host Process.
[2021-11-16 08:21:03.626] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 09:46:29.962] [remoteagent] [info] [::ffff:172.24.192.1][b8ecfbff][ExtensionHostConnection] New connection established.
[2021-11-16 09:46:29.964] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 09:46:29.967] [remoteagent] [info] [::ffff:172.24.192.1][b8ecfbff][ExtensionHostConnection] <2800> Launched Extension Host Process.
[2021-11-16 09:46:29.998] [remoteagent] [info] [::ffff:172.24.192.1][4f87aba8][ManagementConnection] New connection established.
[2021-11-16 09:46:34.453] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 09:46:57.102] [remoteagent] [info] [::ffff:172.24.192.1][fab8d065][ManagementConnection] New connection established.
[2021-11-16 09:46:57.181] [remoteagent] [info] [::ffff:172.24.192.1][0e39568f][ExtensionHostConnection] New connection established.
[2021-11-16 09:46:57.183] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 09:46:57.186] [remoteagent] [info] [::ffff:172.24.192.1][0e39568f][ExtensionHostConnection] <4134> Launched Extension Host Process.
[2021-11-16 09:47:00.523] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 10:57:22.773] [remoteagent] [info] [::ffff:172.24.192.1][1419c1fa][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
[2021-11-16 10:57:23.839] [remoteagent] [info] [::ffff:172.24.192.1][427f594b][ExtensionHostConnection] <332> Extension Host Process exited with code: 0, signal: null.
[2021-11-16 10:57:25.380] [remoteagent] [info] [::ffff:172.24.192.1][fab8d065][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
[2021-11-16 10:57:26.427] [remoteagent] [info] [::ffff:172.24.192.1][0e39568f][ExtensionHostConnection] <4134> Extension Host Process exited with code: 0, signal: null.
[2021-11-16 10:57:29.017] [remoteagent] [info] [::ffff:172.24.192.1][4f87aba8][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
[2021-11-16 10:57:30.069] [remoteagent] [info] [::ffff:172.24.192.1][b8ecfbff][ExtensionHostConnection] <2800> Extension Host Process exited with code: 0, signal: null.
[2021-11-16 10:57:30.069] [remoteagent] [info] Last EH closed, waiting before shutting down
[2021-11-16 10:57:33.099] [remoteagent] [info] [::ffff:172.24.192.1][00e79969][ManagementConnection] New connection established.
[2021-11-16 10:57:33.196] [remoteagent] [info] [::ffff:172.24.192.1][0b2efabe][ExtensionHostConnection] New connection established.
[2021-11-16 10:57:33.198] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 10:57:33.203] [remoteagent] [info] [::ffff:172.24.192.1][0b2efabe][ExtensionHostConnection] <7935> Launched Extension Host Process.
[2021-11-16 10:57:40.647] [remoteagent] [info] [::ffff:172.24.192.1][00e79969][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
[2021-11-16 10:57:41.713] [remoteagent] [info] [::ffff:172.24.192.1][0b2efabe][ExtensionHostConnection] <7935> Extension Host Process exited with code: 0, signal: null.
[2021-11-16 10:57:41.713] [remoteagent] [info] Cancelling previous shutdown timeout
[2021-11-16 10:57:41.713] [remoteagent] [info] Last EH closed, waiting before shutting down
[2021-11-16 10:57:42.140] [remoteagent] [info] [::ffff:172.24.192.1][ba818ac8][ManagementConnection] New connection established.
[2021-11-16 10:57:42.422] [remoteagent] [info] [::ffff:172.24.192.1][63d1584a][ExtensionHostConnection] New connection established.
[2021-11-16 10:57:42.423] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 10:57:42.427] [remoteagent] [info] [::ffff:172.24.192.1][63d1584a][ExtensionHostConnection] <8990> Launched Extension Host Process.
[2021-11-16 10:58:54.645] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 11:00:08.029] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 11:02:41.715] [remoteagent] [info] New EH opened, aborting shutdown
[2021-11-16 11:05:57.204] [remoteagent] [info] [::ffff:172.24.192.1][ba818ac8][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
[2021-11-16 11:05:58.259] [remoteagent] [info] [::ffff:172.24.192.1][63d1584a][ExtensionHostConnection] <8990> Extension Host Process exited with code: 0, signal: null.
[2021-11-16 11:05:58.260] [remoteagent] [info] Last EH closed, waiting before shutting down
[2021-11-16 11:06:01.707] [remoteagent] [info] [::ffff:172.24.192.1][ec64ed7f][ManagementConnection] New connection established.
[2021-11-16 11:06:01.711] [remoteagent] [info] [::ffff:172.24.192.1][5eb8c6ec][ExtensionHostConnection] New connection established.
[2021-11-16 11:06:01.712] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-11-16 11:06:01.717] [remoteagent] [info] [::ffff:172.24.192.1][5eb8c6ec][ExtensionHostConnection] <11294> Launched Extension Host Process.
[2021-11-16 11:06:19.201] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}

richtera · 2021-11-16T16:13:44Z

It works fine in the insider build

Version: 1.63.0-insider (user setup)
Commit: 6a25ae3a24929f35aabf8a051531c0716032e0a0
Date: 2021-11-16T05:14:38.726Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000

The failure is from this exact version.

Version: 1.62.2 (user setup)
Commit: 3a6960b964327f0e3882ce18fcebd07ed191b316
Date: 2021-11-11T20:56:38.428Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000

what's interesting is that after upgrading the insider build to the latest version the normal version started to work again.

brybalicious · 2021-12-09T02:14:38Z

I'm on 1.63.0-insider on WSL2 on windows 10 and still getting this problem when trying to run live-server (which I installed as an npm package using nvm, not a VSCode extension) from a terminal in VSCode Insiders

Version: 1.63.0-insider (user setup)
Commit: 7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e
Date: 2021-12-06T21:54:39.104Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043

Remote Server Logs:

[2021-12-09 02:57:52.395] [remoteagent] [info] 

*
* Visual Studio Code Server
*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license https://aka.ms/vscode-remote/license
*


[2021-12-09 02:57:52.396] [remoteagent] [info] Extension host agent started.
[2021-12-09 02:57:52.549] [remoteagent] [info] [::ffff:127.0.0.1][5f3f8d71][ManagementConnection] New connection established.
[2021-12-09 02:57:54.433] [remoteagent] [info] [::ffff:127.0.0.1][30a82c8d][ExtensionHostConnection] New connection established.
[2021-12-09 02:57:54.554] [remoteagent] [info] Deleted from disk ms-toolsai.jupyter-renderers /home/username/.vscode-server-insiders/extensions/ms-toolsai.jupyter-renderers-1.0.3
[2021-12-09 02:57:59.806] [remoteagent] [info] Deleted from disk ms-toolsai.jupyter /home/username/.vscode-server-insiders/extensions/ms-toolsai.jupyter-2021.11.1001498571
[2021-12-09 02:58:00.670] [remoteagent] [info] Deleted from disk ms-python.vscode-pylance /home/username/.vscode-server-insiders/extensions/ms-python.vscode-pylance-2021.11.2
[2021-12-09 02:58:02.268] [remoteagent] [error] ptyHost was unable to resolve shell environment {}
[2021-12-09 02:58:02.269] [remoteagent] [error] RequestService#request resolving shell environment failed {}
[2021-12-09 02:58:02.270] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-12-09 02:58:02.271] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}
[2021-12-09 02:58:02.442] [remoteagent] [info] [::ffff:127.0.0.1][30a82c8d][ExtensionHostConnection] <7566> Launched Extension Host Process.
[2021-12-09 02:58:20.160] [remoteagent] [error] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed {}

github-actions bot added the new release label Nov 9, 2021

chrmarti assigned alexdima Nov 10, 2021

chrmarti mentioned this issue Nov 10, 2021

[error] RequestService#request resolving shell environment failed {} microsoft/vscode-remote-release#5844

Closed

github-actions bot removed the new release label Nov 10, 2021

chrmarti added bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release labels Nov 10, 2021

chrmarti added this to the October 2021 Recovery 2 milestone Nov 10, 2021

alexr00 mentioned this issue Nov 10, 2021

VsCode in remote a wsl2ubuntu : Can't run yarn tasks since 1.62.1 #136799

Closed

alexdima added the important Issue identified as high-priority label Nov 10, 2021

alexdima changed the title ~~Resolve shell environment failed on 1.62.1 / Remote WSL2~~ Resolve shell environment failed on 1.62.1 Nov 10, 2021

alexdima assigned deepak1556 Nov 10, 2021

bersbersbers mentioned this issue Nov 10, 2021

Some bash commands cannot be found when connected to remote Ubuntu device #136842

Closed

manuelserradev mentioned this issue Nov 10, 2021

Installed JDK is not detecting #136848

Closed

alexdima added the regression Something that used to work is now broken label Nov 10, 2021

alexdima pinned this issue Nov 10, 2021

alexdima removed their assignment Nov 10, 2021

meganrogge mentioned this issue Nov 10, 2021

In WSL mode, the variable 'PATH' set by '/etc/profile' and '~/bash_profile' files is not valid!! #136814

Closed

alexdima mentioned this issue Nov 10, 2021

chore: sync changes from distro/release/1.62 #136877

Merged

deepak1556 closed this as completed Nov 10, 2021

This was referenced Nov 10, 2021

Cannot find "go" binary installed by asdf-vm on WSL golang/vscode-go#1886

Closed

bug #971 is referenced by a current warning message, but is closed without a fix golang/vscode-go#1887

Open

marcusnewton mentioned this issue Nov 11, 2021

remote explorer terminal can't input git password #136825

Closed

chrmarti mentioned this issue Nov 11, 2021

tasks.json via remote container, env vars not passed microsoft/vscode-remote-release#5836

Closed

This was referenced Nov 11, 2021

Environment variables are not inherited after the recent update #136952

Closed

GitHub - auth broken #136953

Open

alexr00 mentioned this issue Nov 11, 2021

WSL Tasks Do Not Inherit/Source Shell Environment #136966

Closed

alexr00 added the verified Verification succeeded label Nov 11, 2021

tanhakabir mentioned this issue Nov 11, 2021

Upgrade to VSC 1.62.1 broke git in remote-ssh microsoft/vscode-remote-release#5863

Closed

Mirko-von-Leipzig mentioned this issue Nov 12, 2021

checkOnSave.overrideCommand fails after updating vscode rust-lang/rust-analyzer#10735

Closed

lramos15 unpinned this issue Nov 12, 2021

gjsjohnmurray mentioned this issue Nov 15, 2021

GitHub Error: remote: no anonymous write access #137161

Closed

github-actions bot locked and limited conversation to collaborators Dec 25, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Resolve shell environment failed on 1.62.1 #136791

Resolve shell environment failed on 1.62.1 #136791

briankintz commented Nov 9, 2021 •

edited by alexdima

Loading

sroby commented Nov 9, 2021 •

edited

Loading

briankintz commented Nov 9, 2021

Taskle commented Nov 9, 2021

ghost commented Nov 10, 2021 •

edited by ghost

Loading

chrmarti commented Nov 10, 2021 •

edited

Loading

chrmarti commented Nov 10, 2021

alexr00 commented Nov 10, 2021

jefferai commented Nov 10, 2021

sroby commented Nov 10, 2021 •

edited

Loading

deepak1556 commented Nov 10, 2021

richtera commented Nov 10, 2021

richtera commented Nov 10, 2021

deepak1556 commented Nov 10, 2021

richtera commented Nov 10, 2021

deepak1556 commented Nov 10, 2021

briankintz commented Nov 10, 2021

taikulawo commented Nov 11, 2021

arobertn commented Nov 11, 2021

Stanzilla commented Nov 13, 2021

aeschli commented Nov 15, 2021

richtera commented Nov 15, 2021

richtera commented Nov 16, 2021

richtera commented Nov 16, 2021 •

edited

Loading

richtera commented Nov 16, 2021

brybalicious commented Dec 9, 2021 •

edited

Loading

Resolve shell environment failed on 1.62.1 #136791

Resolve shell environment failed on 1.62.1 #136791

Comments

briankintz commented Nov 9, 2021 • edited by alexdima Loading

The shell environment no longer resolves correctly in remote terminals in 1.62.1.

A possible workaround is to manually source the shell env in remote terminals

Another workaround is to downgrade to 1.62.0

sroby commented Nov 9, 2021 • edited Loading

briankintz commented Nov 9, 2021

Taskle commented Nov 9, 2021

ghost commented Nov 10, 2021 • edited by ghost Loading

chrmarti commented Nov 10, 2021 • edited Loading

chrmarti commented Nov 10, 2021

alexr00 commented Nov 10, 2021

jefferai commented Nov 10, 2021

sroby commented Nov 10, 2021 • edited Loading

deepak1556 commented Nov 10, 2021

richtera commented Nov 10, 2021

richtera commented Nov 10, 2021

deepak1556 commented Nov 10, 2021

richtera commented Nov 10, 2021

deepak1556 commented Nov 10, 2021

briankintz commented Nov 10, 2021

taikulawo commented Nov 11, 2021

arobertn commented Nov 11, 2021

Stanzilla commented Nov 13, 2021

aeschli commented Nov 15, 2021

richtera commented Nov 15, 2021

richtera commented Nov 16, 2021

richtera commented Nov 16, 2021 • edited Loading

richtera commented Nov 16, 2021

brybalicious commented Dec 9, 2021 • edited Loading

briankintz commented Nov 9, 2021 •

edited by alexdima

Loading

Another workaround is to downgrade to `1.62.0`

sroby commented Nov 9, 2021 •

edited

Loading

ghost commented Nov 10, 2021 •

edited by ghost

Loading

chrmarti commented Nov 10, 2021 •

edited

Loading

sroby commented Nov 10, 2021 •

edited

Loading

richtera commented Nov 16, 2021 •

edited

Loading

brybalicious commented Dec 9, 2021 •

edited

Loading