Skip to content

If the default shell can't be launched and closeOnExit=true, Terminal buys the farm #2563

New issue
New issue
Closed
#3623
Closed
If the default shell can't be launched and closeOnExit=true, Terminal buys the farm#2563
#3623
Assignees
DHowett-MSFT
Labels
Area-TerminalConnectionIssues pertaining to the terminal<->backend connection interfaceIssue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Needs-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.
Milestone
Terminal v0.8
@KAMiKAZOW

Description

@KAMiKAZOW
KAMiKAZOW
opened on Aug 27, 2019

Environment

Windows build number:  10.0.18362.295
Windows Terminal version: 0.4.2382.0

Steps to reproduce

  • Install a WSL distribution (openSUSE Leap 15.0 in my case).
  • Move it to top spot and make it default.
  • Uninstall old WSL distribution and install the upgraded one (openSUSE Leap 15.1 in my case).

Expected behavior

Remove uninstalled WSL distributions. Add all installed WSL distributions unless explicitly disabled in WT.

Actual behavior

WT closes right away. I'm somehow expected to know the UUID change (wsl.exe --list does not show the UUIDs).

Another bug report claims that behavior for non-existent profiles would be handled gracefully in 0.4. Can't confirm that.

Metadata

Metadata

Assignees

Labels

Area-TerminalConnectionIssues pertaining to the terminal<->backend connection interfaceIssue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Needs-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions