Steps to reproduce:
- Install an add-on which imports gui in installTasks at the module level, such as reportPasswords 1.0
Actual behavior:
NVDA crashes and a message is presented informing that NVDA needs to be running to install add-ons.
This maybe produced by a circular import related to gui.contextHelp, according to this old issue. It seems to be fixed following the suggestion provided there by @jcsteh , that is, importing gui at the onInstall() method level.
Expected behavior:
NVDA should be restarted without crashing.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2020.4beta1
Windows version:
10
Name and version of other software in use when reproducing the issue:
n/a
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.
Yes. In previous versions NVDA is restarted without crashing.
If addons are disabled, is your problem still occuring?
Yes.
Did you try to run the COM registry fixing tool in NVDA menu / tools?
Yes.
Steps to reproduce:
Actual behavior:
NVDA crashes and a message is presented informing that NVDA needs to be running to install add-ons.
This maybe produced by a circular import related to gui.contextHelp, according to this old issue. It seems to be fixed following the suggestion provided there by @jcsteh , that is, importing gui at the onInstall() method level.
Expected behavior:
NVDA should be restarted without crashing.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2020.4beta1
Windows version:
10
Name and version of other software in use when reproducing the issue:
n/a
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.
Yes. In previous versions NVDA is restarted without crashing.
If addons are disabled, is your problem still occuring?
Yes.
Did you try to run the COM registry fixing tool in NVDA menu / tools?
Yes.