Step-Over does not returns until i press a key inside the terminal on Ubuntu

[WernerMairl]

System Details

• Operating system name and version:
  Ubuntu 16.04 (current LTS fresh installed) + Ubuntu Desktop

• VS Code version:
  Version 1.12.2
  Date 2017-05-10T13:16:25.899Z
  Shell 1.6.6
  Renderer 56.0.2924.87
  Node 7.4.0

• PowerShell extension version:
  1.2.1

• Output from $PSVersionTable:
  PSVersion 6.0.0-beta
  PSEdition Core
  BuildVersion 3.0.0.0
  CLRVersion
  GitCommitId v6.0.0-beta.1
  OS Linux 4.4.0-78-generic PowerShell crash when breakpoint hit testing DSC resources #99-Ubun...
  Platform Unix
  PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
  PSRemotingProtocolVersion 2.3
  SerializationVersion 1.1.0.1
  WSManStackVersion 3.0

Issue Description

using F10 (Step-Over) to execute a line, the execution seems to hang/never returns!
workaround: set cursor into the terminal and press (any) key: Step-Over comes back and the execution cursor is on the next line... work can be continued.

Observations: the bahavior is not on every line, it seems specially if Write-XXX commands are involved

i'm new on Linux so i'm not sure that i'm doing everything in the right way....
regards
Werner

[daviwil]

This is very strange, thanks for reporting it! I'll take a look.

[WernerMairl]

tell me if or how i can help....

[chrisdias]

i'm seeing this too...pretty much blocks debugging on Linux unless you find this issue in github.

[jackmusick]

#987 Debugger frozen after first breakpoint

This is the same thing as an issue I have open and it's been a problem for a few versions, now. The only difference is that I'm experiencing after stepping into, every other time after pressing enter. This happens on macOS but not Windows.

[marcosowns]

This is the exact same issue I have been experiencing for the last 2 months on Mac OS. Any help here would be appreciated.

[WernerMairl]

Again 3 months later with a fresh/new environment!

BUT NEW BEHAVIOR:
The key-press inside the terminal windows is required for every (exactly) SECOND Step-Over!

Windows 10 HyperV
Ubuntu 16.04 Desktop amd64
installed VSCode (dep download and install via UI)
installed Powershell Core (beta 8) downloading dep and install via UI)

VS-Code 1.17.1
Powershell Plugin 1.4.3
Powershell 6.0.0.beta-8

what are the next steps to solve that ?

• Any trace that i can activate ?
• Any Linux/NodeJs/Atom/VSCode//Powershell expert available that can/will do a debug/inspection session on my machine (TeamViewer,Goto,WebEx whatever)

regards
Werner

[WernerMairl]

next try: fresh installed jessie...same problem/behavior

anyone can confirm that behavior in the same linux versions - or i must assume that i'm causing that by "my way" to install the components ?

• jessie/ubuntu installed - with Keyboard German/AUT
• VS-Code installed by downloading dep => open with Package Manager
• Powershell Core installed by downloading dep => open with Package Manager
• start vscode, install extension, create a few lines of script.. try
  -restart vscode - retry....

Werner