Hi,
Critical alpha regression after merge of #17505:
Steps to reproduce:
- Upgrade from a previous alpha to alpha-35064,605db3e4.
- NVDA displays a configuration error message when restarted.
Actual behavior:
NVDA restores default settings due to value/type mismatch in speak typed characters/words.
Expected behavior:
Speak typed characters and words settings are migrated properly.
NVDA logs, crash dumps and other attachments:
ERROR - config.ConfigManager.initBaseConf (22:10:00.070) - MainThread (28856):
Error loading base configuration; the base configuration file will be reinitialized. A copy of your previous configuration file will be saved at C:\Users\User\AppData\Roaming\nvda\nvda.ini.corrupted.bak
Traceback (most recent call last):
File "config_init.pyc", line 582, in initBaseConf
File "config_init.pyc", line 633, in loadConfig
File "config_init.pyc", line 629, in _loadConfig
File "config\profileUpgrader.pyc", line 27, in upgrade
File "config\profileUpgrader.pyc", line 68, in _doValidation
ValueError: Unable to validate config file after upgrade: Key speakTypedCharacters : the value "False" is of the wrong type.
The above traceback repeats if "speakTypedWords" value/type mismatch occurs (which is on my system as I turn both settings off).
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-35064,605db3e4
Windows version:
Windows 11 24H2 dev Insider (build 26120.2992)
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
Used as a development workstation
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 issues in prior alphas
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
Possible cause:
I suspect config upgrade is at fault in that bool to integer conversion for typing echo settings are not translated correctly.
Thanks.
Hi,
Critical alpha regression after merge of #17505:
Steps to reproduce:
Actual behavior:
NVDA restores default settings due to value/type mismatch in speak typed characters/words.
Expected behavior:
Speak typed characters and words settings are migrated properly.
NVDA logs, crash dumps and other attachments:
ERROR - config.ConfigManager.initBaseConf (22:10:00.070) - MainThread (28856):
Error loading base configuration; the base configuration file will be reinitialized. A copy of your previous configuration file will be saved at C:\Users\User\AppData\Roaming\nvda\nvda.ini.corrupted.bak
Traceback (most recent call last):
File "config_init.pyc", line 582, in initBaseConf
File "config_init.pyc", line 633, in loadConfig
File "config_init.pyc", line 629, in _loadConfig
File "config\profileUpgrader.pyc", line 27, in upgrade
File "config\profileUpgrader.pyc", line 68, in _doValidation
ValueError: Unable to validate config file after upgrade: Key speakTypedCharacters : the value "False" is of the wrong type.
The above traceback repeats if "speakTypedWords" value/type mismatch occurs (which is on my system as I turn both settings off).
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-35064,605db3e4
Windows version:
Windows 11 24H2 dev Insider (build 26120.2992)
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
Used as a development workstation
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 issues in prior alphas
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
Possible cause:
I suspect config upgrade is at fault in that bool to integer conversion for typing echo settings are not translated correctly.
Thanks.