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

Terminal closes to update without asking permission #5622

Closed
aleksey-hoffman opened this issue Apr 28, 2020 · 8 comments
Closed

Terminal closes to update without asking permission #5622

aleksey-hoffman opened this issue Apr 28, 2020 · 8 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@aleksey-hoffman
Copy link

aleksey-hoffman commented Apr 28, 2020

Environment

Windows build number: Version 10.0.18363.752
Windows Terminal version (if applicable): 0.11.1121.0

Steps to reproduce

Have the terminal app open

Expected behavior

Am I seeing things, or does terminal automatically closes to update without asking permission? It happend to me for the 2nd time.

When I got back to my computer, I realised that my running server was stopped because the terminal app was closed, turns out it got updated (as always its icon was in the "stuck progress" state, but that's a Windows 10 bug and is not related to this issue)

image

Actual behavior

Terminal closes automatically to update without asking permission.

@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 Apr 28, 2020
@DHowett-MSFT

This comment has been minimized.

@aleksey-hoffman
Copy link
Author

@DHowett-MSFT sorry mate, I edited it out.
It's just I lost too much unsaved work too many times because of Windows 10 restarting without asking permission after updating while I was away from the computer.

@DHowett-MSFT
Copy link
Contributor

I know, it’s pretty crappy. We haven’t yet cracked the API that lets us tel the store to hold off yet. We try, though, when there are multiple tabs open. I’ve seen reports that clicking “cancel” in the “are you sure you want to close all these fine tabs?” dialog just makes the store kill us instead of waiting :/

@DHowett-MSFT
Copy link
Contributor

(Also, thank you. I’ve filed bugs out of anger, and I always feel bad afterwards. Sorry we made you lose some work :()

@zadjii-msft
Copy link
Member

There's also #3915 - maybe we should dupe this thread?

@aleksey-hoffman
Copy link
Author

@DHowett-MSFT yeah thanks for understanding. I know we shouldn't get annoyed by stuff like this, you guys are doing your best, you made the app open source, you are improving it every day, what is there more to ask, it takes time, you guys are doing a good job!

I suppose we can dupe this thread since there's a similar one opened, I didn't see it.

@zadjii-msft
Copy link
Member

Thanks!

/dup #3915

@ghost
Copy link

ghost commented Apr 28, 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 Apr 28, 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 Apr 28, 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