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

NVDA process is killed when closing a terminal window from the close button #15404

Open
jmdaweb opened this issue Sep 8, 2023 · 4 comments
Open
Labels
app/windows-console Legacy console in Windows, potentially will superseded by the app/windows-terminal app/windows-terminal New terminal app, potentially supersedes app/windows-console (repo: microsoft/terminal) p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@jmdaweb
Copy link

jmdaweb commented Sep 8, 2023

Steps to reproduce:

  1. Open a console window, such as Git bash or cmd.
  2. Move the navigator object or the mouse to the window close button.
  3. Activate / click the button.

Actual behavior:

The console window is closed and NVDA process is killed.

Expected behavior:

NVDA should continue running after closing the window, as it does when closing from the window menu or typing the command exit.

NVDA logs, crash dumps and other attachments:

Original reporters will attach logs if possible.

System configuration

NVDA installed/portable/running from source:

Installed and portable.

NVDA version:

2023.1 and 2023.2

Windows version:

Windows 10 22H2 build 19045.3324 and Windows 10 build 21H2 19044.2132.

Name and version of other software in use when reproducing the issue:

A console window which uses conhost as the terminal engine.

Other information about your system:

N/A

Other questions

Does the issue still occur after restarting your computer?

Yes.

Have you tried any other versions of NVDA? If so, please report their behaviors.

No, but I have tried other Windows versions. This issue has no impact on Windows 11.

If NVDA add-ons are disabled, is your problem still occurring?

Yes.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes.

@jmdaweb
Copy link
Author

jmdaweb commented Sep 8, 2023

CC: @aguirremdp

@XLTechie
Copy link
Collaborator

XLTechie commented Sep 8, 2023 via email

@Brian1Gaff
Copy link

Brian1Gaff commented Sep 9, 2023 via email

@seanbudd
Copy link
Member

Duplicate of #1682, however as this is still the behaviour by default, I think this should remain open

@seanbudd seanbudd added p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority app/windows-terminal New terminal app, potentially supersedes app/windows-console (repo: microsoft/terminal) app/windows-console Legacy console in Windows, potentially will superseded by the app/windows-terminal triaged Has been triaged, issue is waiting for implementation. labels Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app/windows-console Legacy console in Windows, potentially will superseded by the app/windows-terminal app/windows-terminal New terminal app, potentially supersedes app/windows-console (repo: microsoft/terminal) p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

No branches or pull requests

4 participants