Skip to content
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

Pressing ALT+SHIFT+D to split the current pane into two panes causes PWSH to start incorrectly #9119

Closed
JasonWThompson opened this issue Feb 11, 2021 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@JasonWThompson
Copy link

Environment

OS Version:
[Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0

Terminal version: 
Windows Terminal Preview
Version: 1.6.10272.0

Any other software?

pwsh --version
PowerShell 7.1.1

Steps to reproduce

Open up a tab configured to start with Powershell 7.1.1. Press ALT+SHIFT+D

Expected behavior

A new Powershell instance starts in a separate pane.

Actual behavior

I get a pane that says [error 0x8007010b when launching `pwsh.exe']

Other notes

Splitting the broken pane creates a working pane. Splitting that pane gives a broken pane. And so on...

Additionally splitting the pane with ALT+SHIFT+- or ALT+SHIFT+= works every time.

Here's an example of me splitting the pane over and over again. You may need to zoom out since this is from my 4k screen.

image

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 11, 2021
@JasonWThompson
Copy link
Author

I didn't notice this when initially searching for the issue, but this is very similar to #9114 The only difference is that the author of #9114 is duplicating the tab and I'm splitting the pane. I'm guessing the cause is the same.

@zadjii-msft
Copy link
Member

Yep, these are the same root cause, which is fundamentally #8930.

/dup #8930

@ghost
Copy link

ghost commented Feb 11, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Feb 11, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 11, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants