-
Notifications
You must be signed in to change notification settings - Fork 854
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL does not get focus when launching from taskbar #3443
Comments
Seeing the same issue on windows 10.0.16299.551 |
So if CMD is able to focus but WSL is not, I would say check https://github.com/Microsoft/Console/issues/. I think this was addressed in Insiders but it wouldn't hurt to file it over there for verification. |
thanks @DarthSpock for the suggestion. I just created issue 233 in the Console project. |
Please see the related issues #2597 and #3123, which were replaced by microsoft/terminal#179 |
The "console" tag is at best loose on this one. It isn't terminal emulation related (console proper) and it certainly isn't Linux kernel ABI related (WSL proper). The label just qualifies the redirect since microsoft/terminal#179 is open. |
Please fill out the below information:
Your Windows build number: (Type
ver
at a Windows Command Prompt)17134
What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
If an instance of WSL is running, to run another copy: right-click on the running instance in Taskbar, and select the instance name (i.e., Ubuntu).
What's wrong / what should be happening instead:
In all other apps (including cmd.exe), the new instance immediately takes focus. With WSL, explorer.exe retains focus and requires either alt-tab to the WSL window or clicking in the WSL window.
Strace of the failing command, if applicable: (If
some_command
is failing, then runstrace -o some_command.strace -f some_command some_args
, and link the contents ofsome_command.strace
in a gist here).N/A
For WSL launch issues, please collect detailed logs.
Don't imagine logs are needed as I've repro'd this easily on builds from 16299 all the way through 17134.
See our contributing instructions for assistance.
The text was updated successfully, but these errors were encountered: