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 goes away without errors or warnings #18561

Open
danie-dejager opened this issue Feb 11, 2025 · 5 comments
Open

Terminal goes away without errors or warnings #18561

danie-dejager opened this issue Feb 11, 2025 · 5 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@danie-dejager
Copy link

Windows Terminal version

1.21.10351.0

Windows build number

10.0.26100.3037

Other Software

No response

Steps to reproduce

  1. Open Terminal.
  2. Open multiple tabs.
  3. Click on any of the tabs and drag the tab out of the terminal window.
    Terminal will close down. This sometimes happen randomly that the window will just completely close down and I lose all my work. The only repeatable way I found is to click and move a tab in Terminal. This happened to me on previous versions of Terminal too.

Expected Behavior

Either move the main Terminal window or detach the selected tab from the terminal window.
Terminal should not close down (at least without warning) as all my sessions are then dead and gone.

Actual Behavior

Terminal closes itself without warning or error.

@danie-dejager danie-dejager added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Feb 11, 2025
@JEDIZECH10
Copy link

JEDIZECH10 commented Feb 11, 2025

Dear @danie-dejager,
I would love to help with that! Could you please respond with the windows version (e.g. windows 11, 10 etc), steps to reproduce the issue, and the conditions that made the issue happen please?

  • JEDIZECH10

@zadjii-msft
Copy link
Member

We've seen this before in #15689 - @danie-dejager any chance you're in some sort of corporate environment with BeyondTrust running/? Are you running elevated? With EnableLUA=0?
Does it happen:

  • When you click & hold on the tab?
  • Once you've started moving it (but still inside the tab row)?
  • Once you drag it out of the window?
  • At the moment you drop it (either inside or outside the tab row)?

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Feb 12, 2025
@JEDIZECH10
Copy link

JEDIZECH10 commented Feb 13, 2025 via email

@danie-dejager
Copy link
Author

danie-dejager commented Feb 13, 2025

*> Are you running elevated?
Switching around did not make a difference.

  • corporate environment with BeyondTrust running/?
    We are using BeyondTrust.
Active Policies
	1. PMC

System Info
	Client version: 23.3.130.0
	PMC adapter version: 23.3.256
  • With EnableLUA=0
    I won't be allowed to change that.
  • When you click & hold on the tab?
    No. Have to start moving it.
  • Once you've started moving it (but still inside the tab row)?
    Yes
  • Once you drag it out of the window?
    Yes
  • At the moment you drop it (either inside or outside the tab row)?
    Just moving it will close it down.

Sometimes it closes itself and I can't say that I was busy dragging the tab at that time. Sometimes if feels that it just closed randomly.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Feb 13, 2025
@JEDIZECH10
Copy link

JEDIZECH10 commented Feb 13, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

3 participants