vscode-powershell: Powershell integrated terminal in VSCode doesn't start up.
System Details
- Operating system name and version: Ubuntu 16.04
- VS Code version: 1.25.0
- PowerShell extension version: 1.8.0
- Output from
$PSVersionTable: (see below)
Copy / paste the following commands into the PowerShell Integrated Console, and paste the output here:
As I can't start the integrated terminal, I ran these commands in normal powershell, ran via bash.
code -v
1.25.0
0f080e5267e829de46638128001aeb7ca2d6d50e
x64
$pseditor.EditorServicesVersion
<no output>
code --list-extensions --show-versions
AureliaEffect.aurelia@1.0.3
behzad88.Aurelia@1.2.2
christian-kohler.path-intellisense@1.4.2
EditorConfig.EditorConfig@0.12.4
ms-vscode.csharp@1.15.2
ms-vscode.PowerShell@1.8.0
msjsdiag.debugger-for-chrome@4.7.0
steoates.autoimport@1.5.3
$PSVersionTable
Name Value
---- -----
PSVersion 6.1.0-preview.2
PSEdition Core
GitCommitId v6.1.0-preview.2
OS Linux 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Issue Description
I had a working Powershell integrated terminal and debugger just yesterday, using the old version of the Powershell extension.
VS code had a non clean exit (As my system locked up).
This morning I started Visual Studio Code and the integrated terminal doesn’t work. Neither does the debugger. The Powershell extension also updated today.
After the terminal tries to launch it shows:
PowerShell Integrated Console Permissions to the pipe file were not set properly. Expected: 600 Actual: srw------- for file: /tmp/CoreFxPipe_PSES_5b0a428f-e0b7-4e90-b8c8-d0a44966a752
And after a while the terminal closes. Logs below:
the pwsh app seems to work fine in normal bash.
I tried to delete all the pipe like files with the following command:
rm /tmp/CoreFxPip* in the hope that it would re-create them correctly, but that didn’t make a difference.
I tried to set the permissions correctly on the file it was complaining about (by running chmod 600 on the file it was complaining about) but that doesn’t seem to work: it seems to re-create the files with incorrect permissions.
Running VSCode as root doesn’t seem to help either (glad it is very loud about warning the user not to do this).
I did find this old issue but this seems to be more windows specific.
Attached Logs
2018-7-11 08:39:32 [NORMAL] - Syntax Folding Provider registered
2018-7-11 08:39:32 [NORMAL] - powershell.exe started, pid: 8751
2018-7-11 08:39:38 [NORMAL] - powershell.exe terminated or terminal UI was closed
2018-7-11 08:40:32 [NORMAL] - Language server startup failed.
2018-7-11 08:40:32 [ERROR] - The language service could not be started:
2018-7-11 08:40:32 [ERROR] - Timed out waiting for session file to appear.
Verbose logs attached. logs.zip
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 34 (7 by maintainers)
Looks good for now. Terminal starts up, and debugging looks more stable. Thanks
If you use PowerShell 7, this will go away… but I also have PR out to fix this: https://github.com/PowerShell/PowerShellEditorServices/pull/1200
We no longer rely on stat in the PowerShell Preview (coming to Stable next month)
So you shouldn’t have to do this if you use that. 😊
see https://github.com/PowerShell/vscode-powershell/issues/1421
./modules/PowerShellEditorServices/Start-EditorServices.ps1:227
replace
to