Split terminal error

[damianoazzolini]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version:

Version: 1.58.0-insider (user setup)
Commit: 2d23c42a936db1c7b3b06f918cde29561cc47cd6
Date: 2021-07-07T12:09:55.219Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.19042

• OS Version: Windows 10 version 20H2 build 19042.1052

I'm connected with ssh into a server with installed CentOS Linux release 7.7.1908

Steps to Reproduce:

1. Open integrated terminal
2. Split terminal
3. Create new terminal (with the +) and move into this new terminal
4. Split terminal

At step 4 I get an error ''The terminal process failed to launch: Starting directory (cwd) "\home\userrname\test" does not exist''. It seems that the second terminal tries to open a folder but with the path specified with \ instead of / (the first split operation, step 2, works well). /home/userrname/test does exists, and it is the default location of a new terminal

[vscodebot]

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

• Test: Terminal editors - Split terminal does not work (#127633)
• Possible bug with the split terminal feature (#123361)

[damianoazzolini]

#127633 states that nothing happens
#123361 states that the layout is messy

[ranshalit]

I also observe the same error after recent update

[meganrogge]

I can't reproduce this. Please provide a gif

[spasche]

Hello,

I'm also affected, here are some steps to reproduce.
I could see that it only happens when you have a workspace with multiple folders.

Pre-conditions:

• vscode running on Windows, tested with version 1.58.2
• linux server accessible from ssh

1. Prepare the linux server

ssh user@ubu-dev
mkdir /tmp/folder0 /tmp/folder1
cat << EOF > /tmp/myworkspace.code-workspace
{
        "folders": [
                {
                        "path": "folder1"
                },
                {
                        "path": "folder2"
                }
        ]
}
EOF
exit

2. From Windows, open the remote workspace

code --user-data-dir=c:\tmp\clean_profile --file-uri vscode-remote://ssh-remote+user@ubu-dev/tmp/myworkspace.code-workspace

3. Open a terminal, select folder1
4. Run command: Terminal: Split terminal

Video: https://1drv.ms/v/s!AloPbwYP-ZZVhYEtHc8CDxXT7yU38g?e=FoI6dc

[lithsin]

I also have the same problem for remote workspaces with multiple folders. The first terminal can be opened without any problem, but a subsequent split terminal at the same location will result in the error message shown below. I can confirm that the folder does exist (otherwise the first terminal couldn't have been opened), and remote workspaces with only one folder do not suffer from this problem.

[jchang10]

#127811 is the same. Bummer no solution yet.

[Tyriar]

@jchang10 thanks for the link, that one makes it pretty clear the is splitCwd problem is

/duplicate

[cj-clifton]

Also facing this issue, I can start new terminals but they cannot be split

[Melirius]

More mystery to the topic: 1) if I set sh as default terminal, it can be split, and even bash terminal can be split, providing another sh terminal; 2) if I set sh as default terminal, start bash terminal, change default to bash, this already started bash terminal can be split providing another bash terminal without problem; 3) if I set bash as default terminal and start bash terminal, it cannot be split. Log does not provide any details:

[2021-08-24 12:48:31.942] [renderer1] [trace] Spawning remote agent process {"terminalId":41}
[2021-08-24 12:48:32.054] [renderer1] [debug] Terminal process ready (shellProcessId: 9421)
[2021-08-24 12:48:33.686] [renderer1] [trace] terminalInstance#ctor (instanceId: 17) {"cwd":{"$mid":1,"path":"/home/ivan","scheme":"vscode-remote"}}
[2021-08-24 12:48:34.079] [renderer1] [debug] Terminal process exit (instanceId: 17) with code undefined
[2021-08-24 12:48:34.079] [renderer1] [debug] Terminal process exit (instanceId: 17) state 2
[2021-08-24 12:48:34.082] [renderer1] [trace] terminalInstance#dispose (instanceId: 17)

[spasche]

@Melirius: this is fixed in 1.60 (currently in the Insiders Build).