Unable to immediately start typing after starting new window from context menu

[wkbrd]

Starting a new Ubuntu/openSUSE window from the context menu does not allow for immediate text entry. The legacy "bash on Ubuntu on Windows" does not exhibit this problem and allows for immediate text input. A workaround is to click the window using the mouse, touch the window, or switch windows using Alt-Tab and back.

• Your Windows build number: 10.0.16299.19

• What you're doing and what's happening:
  Right-click on Ubuntu or openSUSE taskbar icon. Click on application name (e.g., Ubuntu). Console window appears. Then try to immediately type something, like "ls". The text entered does not appear in the console window.

• What's wrong / what should be happening instead:
  The text input should appear in the window rather than being lost.

• Strace of the failing command, if applicable: N/A

[wkbrd]

Additionally, when opening the console window as reproduced above, the window appears to not be the focused window (as it does not contain the accent color around the edge of the window).

[wkbrd]

FYI, this also reproduces with 10.0.17035.1000.

[wkbrd]

Update: This still reproduces with 10.0.17123.1.

[wkbrd]

Update: This still reproduces with 10.0.17134.1.

[WSLUser]

@zadjii-msft probably hasn't been made aware of this issue since this wasn't correctly filed in Console

[patrikhuber]

Still repros in 10.0.17134.48.

[zadjii-msft]

(For the record, I'm not triaging the WSL github page anymore - any console issues should be filed over at https://github.com/Microsoft/Console)

I'm not seeing this repro on 17670 (internally) but that doesn't necessarily mean it's fixed. It's definitely not behavior that we control - it sounds like the shell has decided not to focus our window in that case. I can keep an eye out for it.

[patrikhuber]

@zadjii-msft Thank you for the reply. Where should we post/report this then so that it gets the appropriate attention? Thanks!

[WSLUser]

Both myself and @zadjii-msft provided the link...

[patrikhuber]

@DarthSpock Oh well I am sorry that I asked where to report a bug and that I do not know what "Console" is or how it is related to WSL...

[zadjii-msft]

The "Console", or conhost.exe, is the window that runs all commanline applications in Windows. So bash, cmd, powershell, they're all running attached to conhost.exe, which is responsible for rendering the "terminal".

https://github.com/microsoft/console is "the official Windows Console issues & samples repo", for all your console related issues. We used to have both console and WSL issues in the WSL repo, but that ended up creating a lot of extra noise for both teams, so we've pulled them apart now.

[patrikhuber]

@zadjii-msft Cool! Thank you very much for the thorough and very interesting explanation! :-)

[bitcrazed]

Thanks for reporting this issue @patrikhuber. Appreciate your patience - we have several repo's & try to direct issues to the teams that most closely own/relate to the issue at hand.

As @zadjii-msft states, Windows Console == the Terminal app on Linux or Mac. Console is responsible for sending keystrokes & input to the command-line app/tool/shell (e.g. Cmd, PowerShell, Linux/WSL) that it's connected to, and for rendering the text returned by the app/tool/shell.

I can confirm that I can repro this issue and will work with @zadjii-msft to debug and diagnose. We'll reply in the microsoft/terminal#179 issue.

Closing this issue - please follow the master thread here: microsoft/terminal#179

[mariusstrom]

@zadjii-msft FYI I'm also at MSFT and I have a repro. Feel free to ping me on corpnet if you need to see a repro.

[bitcrazed]

Thanks for the info @mariusstrom - but please note - this issue in this repo is not being monitored by the Console team. Please head over to the microsoft/terminal#179 issue to track progress.