Change:
Type: <bBug</bThe terminal cannot be opened when multiple users use remote-ssh When I used Remote-SSH today, I found that the terminal could not be opened. After checking the log, I found the following error output: Since the terminal I use is , vscode-server copies my to , and the permission of this file belongs to me. As a result, the other users who use as the terminal cannot open the terminal when using Remote-SSH for no permission to overwrite this file. And I find that when the user uses bash, vscode-server does not copy to . Therefore, this bug does not exist when is used by all users VS Code version: Code 1.70.0 (, 2022-08-04T04:38:55.829Z) OS version: Darwin x64 20.6.0 Modes: Remote OS version: Linux x64 5.4.0-122-generic Remote OS version: Linux x64 5.4.0-122-generic <details<summarySystem Info</summary </details<details<summaryExtensions (10)</summaryExtensionVersion ------ pythonsnippets1.0.2 vscode-language-pack-zh-hans1.70. jupyter-keymap1.0.0 remote-containers0.241.3 remote-ssh0.84.0 remote-ssh-edit0.80.0 material-icon-theme4.19.0 svg-preview2.8.3 jinja0.0.8 material-theme3.15.2 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
EDIT: I found the log... I encountered the same problem. When upgrading to 1.70 the zsh shell only opens for the first remote user...
You can find the error log in of , as shown below. <img width="1099" alt="" src="https://user-"After I rolled the software back to the previous version, the issue was solved.
Thx, I found the log also now. Rolling back to 1.69.2 and disabling auto update of VSCode solves the problem currently... I hope the VSCode team will take care of this issue, for the next release
I tried also to find the line which is copying the file in the script, but was not really able to find it... I believe the command is hidden somewhere in the method
Thanks for the report, you can workaround this by disabling shell integration automatic injection with and then in your :
thanks, your workaround works!
yes thanks, I was having to go back to the previous release until sent me here!
This is fixed in that it will no longer block the terminal from being created, as called out in though we need to make sure that multiple users are able to write the same file. We could perhaps solve this by moving the zsh shell integration files into their own folder in the bundle and just use that?
is this workaround still valid or should we be waiting for an update in vs code?
it's fixed in insider's it's reopened bc of some complications that the fix has caused

Discussion:
if (injection.filesToCopy) { for (const f of injection.filesToCopy) { await fs.mkdir(path.dirname(f.dest), { recursive: true }); <del> await fs.copyFile(f.source, f.dest); </del> <ins> try { await fs.copyFile(f.source, f.dest); } catch { // Swallow error, this should only happen when multiple users are on the same // machine. Since the shell integration scripts rarely change, plus the other user // should be using the same version of the server in this case, assume the script is // fine if copy fails and swallow the error. } </ins> } } } else {

const zdotdir = path.join(tmpdir(), 'vscode-zsh'); await fs.mkdir(zdotdir, { recursive: true }); const source = path.join(path.dirname(FileAccess.asFileUri('', require).fsPath), 'out/vs/workbench/contrib/terminal/browser/media/shellIntegration-rc.zsh'); <del> await fs.copyFile(source, path.join(zdotdir, '.zshrc')); </del> <ins> // TODO: Does filesToCopy make this unnecessary now? try { await fs.copyFile(source, path.join(zdotdir, '.zshrc')); } catch { // Swallow error, this should only happen when multiple users are on the same // machine. Since the shell integration scripts rarely change, plus the other user // should be using the same version of the server in this case, assume the script is // fine if copy fails and swallow the error. } </ins> this._ptyOptions.env = this._ptyOptions.env || {}; this._ptyOptions.env['ZDOTDIR'] = zdotdir; delete this._ptyOptions.env['_ZDOTDIR'];