You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platform ServicePack Version VersionString
-------- ----------- ------- -------------
Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal -- Version: 1.1.2233.0
Steps to reproduce
run ubuntu 20.04 and then type exit from ubuntu terminal
Expected behavior
return to windows terminal without problem.
Actual behavior
Sometimes it shows me [process exited with code 130], but not every time.
I don't know what kind of other log I need to provide.
It happens on every workstation I used , and just some times
The text was updated successfully, but these errors were encountered:
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
Aug 16, 2020
See issue #5214. This is typically the result of some previous application having set the shell error code to 130, and that's what is reported when you exit. If you don't want to see those errors you can set the "closeOnExit" setting to "always".
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
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
Aug 17, 2020
Environment
Windows Terminal -- Version: 1.1.2233.0
Steps to reproduce
run ubuntu 20.04 and then type exit from ubuntu terminal
Expected behavior
return to windows terminal without problem.
Actual behavior
Sometimes it shows me [process exited with code 130], but not every time.
I don't know what kind of other log I need to provide.
It happens on every workstation I used , and just some times
The text was updated successfully, but these errors were encountered: