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

Improper initialization of UIA during NVDA start #13347

Closed
zstanecic opened this issue Feb 16, 2022 · 4 comments
Closed

Improper initialization of UIA during NVDA start #13347

zstanecic opened this issue Feb 16, 2022 · 4 comments
Assignees

Comments

@zstanecic
Copy link
Contributor

Steps to reproduce:

  1. Start or restart NVDA.
  2. See the log.
    INFO - main (15:43:24.276) - MainThread (21816):
    Starting NVDA version alpha-24688,af3b8440
    INFO - core.main (15:43:24.339) - MainThread (21816):
    Config dir: C:\Users\ninos\AppData\Roaming\nvda
    INFO - config.ConfigManager._loadConfig (15:43:24.340) - MainThread (21816):
    Loading config: C:\Users\ninos\AppData\Roaming\nvda\nvda.ini
    INFO - core.main (15:43:24.427) - MainThread (21816):
    Windows version: Windows 11 21H2 (10.0.22000) workstation
    INFO - core.main (15:43:24.427) - MainThread (21816):
    Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)]
    INFO - core.main (15:43:24.428) - MainThread (21816):
    Using comtypes version 1.1.8
    INFO - core.main (15:43:24.428) - MainThread (21816):
    Using configobj version 5.1.0 with validate version 1.0.1
    INFO - synthDrivers.espeak.SynthDriver.init (15:43:24.737) - MainThread (21816):
    Using eSpeak NG version 1.51-dev
    INFO - synthDriverHandler.setSynth (15:43:24.818) - MainThread (21816):
    Loaded synthDriver espeak
    INFO - core.main (15:43:24.818) - MainThread (21816):
    Using wx version 4.1.1 msw (phoenix) wxWidgets 3.1.5 with six version 1.16.0
    INFO - brailleInput.initialize (15:43:24.820) - MainThread (21816):
    Braille input initialized
    INFO - braille.initialize (15:43:24.821) - MainThread (21816):
    Using liblouis version 3.20.0
    INFO - braille.initialize (15:43:24.824) - MainThread (21816):
    Using pySerial version 3.5
    INFO - braille.BrailleHandler.setDisplayByName (15:43:24.834) - MainThread (21816):
    Loaded braille display driver noBraille, current display has 0 cells.
    INFO - core.main (15:43:25.054) - MainThread (21816):
    Java Access Bridge support initialized
    INFO - UIAHandler.UIAHandler.MTAThreadFunc (15:43:25.167) - UIAHandler.UIAHandler.MTAThread (21952):
    UIAutomation: IUIAutomation6
    ERROR - NVDAHelperLocal (15:43:25.309) - UIAHandler.UIAHandler.MTAThread (21952):
    Thread 21952, build\x86\UIARemote\UIARemote.cpp, initialize, 141:
    Error activating activation context for C:\Program Files (x86)\NVDA\lib\alpha-24688,af3b8440\Microsoft.UI.UIAutomation.dll.manifest

INFO - core.main (15:43:25.394) - MainThread (21816):
NVDA initialized

Actual behavior:

NVDA starts with error above, which also has the impact when navigating word documents.

Expected behavior:

No errors.

System configuration

NVDA installed/portable/running from source:

installed

NVDA version:

Starting NVDA version alpha-24688,af3b8440
NVDA version alpha-24688,af3b8440

Windows version:

Windows 11 21H2 (10.0.22000) workstation

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

Microsoft word version 16.0.14827.20186 - 64 bit

Other information about your system:

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.

yes, previous version of alpha, no problem in previous version whatsoever

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?

not applicable

@seanbudd
Copy link
Member

Possibly caused by #13283 and fixed by #13350.
Can you confirm that this is fixed by updating to the next alpha build? The next alpha with the fix is still building, but it should be ready in 30min.

cc @michaelDCurran

@seanbudd
Copy link
Member

@MarcoZehe
Copy link
Contributor

I can confirm that this is fixed in the latest alpha. I was also seeing that error yesterday, but after updating, it is gone.

@feerrenrut
Copy link
Contributor

Closing as fixed with revert (see PR #13350)

michaelDCurran added a commit that referenced this issue Feb 24, 2022
…Word via UIA, using UIA remote ops (#13387)

This reintroduces the commits in pr #13283 which had been reverted in pr #13350. However it also addresses build issues.

Summary of the issue:
PR #13283 introduced support for reporting line/column/section numbers in Microsoft word via UI Automation, by using the UI Automation Remote Operations Library.
However, this PR had to be reverted in #13350 as
1. UIA would not initialize properly in binary builds due to a missing manifest file. (Improper initialization of UIA during NVDA start #13347)
2. NVDA failed to build on Visual Studio 2022. Specifically when building the Remote Ops library with msbuild, midl would fail with an error about a system environment variable being missing.
3. NVDA could no longer be built on Windows 7. (Impossible to build NVDA after introduction of UIA remote library #13346)

Description of how this pull request fixes the issue:
This PR reintroduces all of the original changes, but:
• setup.py now includes *.manifest files in the lib directory.
• NVDA again now requires Visual Studio 2019. However, builds will not fail if a newer version of Visual Studio (E.g. 2022) is installed along side 2019. this is managed by setting MSVC_VERSION in scons before it looks for Visual Studio, so that it specifically selects VS 2019 (VC 14.2).
Although building on Windows 7 could not be fixed, the readme now notes that only building on Windows 10 and higher is supported.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants