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

[process exited with code 130] #7306

Closed
tlsalex opened this issue Aug 16, 2020 · 3 comments
Closed

[process exited with code 130] #7306

tlsalex opened this issue Aug 16, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@tlsalex
Copy link

tlsalex commented Aug 16, 2020

Environment

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

@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 Aug 16, 2020
@j4james
Copy link
Collaborator

j4james commented 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".

@zadjii-msft
Copy link
Member

Yea, @j4james is right about this one. There's more discussion over in #5214, so I'll redirect you over there. Thanks!

/dup #5214

@ghost
Copy link

ghost commented Aug 17, 2020

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 Aug 17, 2020
@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 Aug 17, 2020
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

3 participants