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

Bug Report: Terminal won't start if profile's commandline points to non-existing exe #1458

Closed
garyng opened this issue Jun 23, 2019 · 1 comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@garyng
Copy link

garyng commented Jun 23, 2019

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.30]
Windows Terminal version: 0.2.1715.0

Steps to reproduce

  1. Install, launch and close Windows Terminal
  2. Uninstall PowerShell Core
  3. Launch Windows Terminal again

Expected behavior

  1. Windows Terminal should start

Actual behavior

  1. It crashes

Workaround

Force Terminal to generate a new profiles.json by deleting it.

@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 Jun 23, 2019
@garyng garyng changed the title Bug Report: Terminal won't start if profile does Bug Report: Terminal won't start if profile doesn' Jun 23, 2019
@garyng garyng changed the title Bug Report: Terminal won't start if profile doesn' Bug Report: Terminal won't start if profile does not exist Jun 23, 2019
@garyng garyng changed the title Bug Report: Terminal won't start if profile does not exist Bug Report: Terminal won't start if profile's commandline points to non-existing exe Jun 23, 2019
@DHowett-MSFT
Copy link
Contributor

This's #982.

@DHowett-MSFT DHowett-MSFT added Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Area-Settings Issues related to settings and customizability, for console or terminal and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 27, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. 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