-
Notifications
You must be signed in to change notification settings - Fork 9k
Closed
Labels
Area-AccessibilityIssues related to accessibilityIssues related to accessibilityIssue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Product-ConhostFor issues in the Console codebaseFor issues in the Console codebaseResolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.
Milestone
Description
Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] 21H1 (19603.1000)
Windows Terminal version (if applicable): inbox console
Any other software? NVDA 2020.2
Steps to reproduce
- Start the latest NVDA alpha snapshot.
- In NVDA advanced settings, enable "use UI Automation to access the Windows Console when available".
- Open cmd.
- Ssh to an Ubuntu 18.04 system.
- Run
sudo do-release-upgrade -d.
Expected behavior
NVDA reads the output, and the console remains functional.
Actual behavior
Windows Console crashes, and the following is written to the NVDA log:
ERROR - eventHandler.executeEvent (04:42:19.980) - MainThread (21752):
error executing event: caret on <NVDAObjects.Dynamic_WinConsoleUIAEditableTextWithAutoSelectDetectionUIA object at 0x070733B0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 155, in executeEvent
File "eventHandler.pyc", line 92, in __init__
File "eventHandler.pyc", line 100, in next
File "NVDAObjects\behaviors.pyc", line 191, in event_caret
File "editableText.pyc", line 333, in detectPossibleSelectionChange
File "editableText.pyc", line 340, in _updateSelectionAnchor
File "NVDAObjects\UIA\__init__.pyc", line 776, in compareEndPoints
File "comtypesMonkeyPatches.pyc", line 26, in __call__
_ctypes.COMError: (-2147418113, 'Catastrophic failure', (None, None, None, 0, None))
Context
NVDA uses cursor changed events to detect and report selection changes to the user. It receives a cursor change event and compares the previous and current selection endpoints, which causes console to crash in this case. Is there anything I can do to help trace this on the console side?
Please push the fix for this issue to 21H1 as we'd really like to use UIA in console (especially after the excellent work in #4018 and #4495)!
Metadata
Metadata
Assignees
Labels
Area-AccessibilityIssues related to accessibilityIssues related to accessibilityIssue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Product-ConhostFor issues in the Console codebaseFor issues in the Console codebaseResolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.