Skip to content

Will NVDA 2023.1 have to reset the user's default configuration? #14412

@cary-rowen

Description

@cary-rowen

When I upgraded from nvda2022.4Beta3 to alpha-27213, I encountered a warning about a bad configuration file.

Steps to reproduce:

Upgrade NVDA from older version to alpha-27213,

Actual behavior:

I got a warning that my configuration is wrong and my configuration has been reset.
The specific error configuration is 'reportLineIndentation'.

Expected behavior:

We should have a solution that has the least impact on users.
Also, even if the configuration file is wrong, please help the user to keep the log containing the error instead of directly resetting to the default value.

NVDA logs, crash dumps and other attachments:

ERROR - config.ConfigManager._initBaseConf (12:19:28.720) - MainThread (3500):
Error loading base configuration
Traceback (most recent call last):
  File "config\__init__.pyc", line 565, in _initBaseConf
  File "config\__init__.pyc", line 599, in _loadConfig
  File "config\__init__.pyc", line 595, in _loadConfig
  File "config\profileUpgrader.pyc", line 25, in upgrade
  File "config\profileUpgrader.pyc", line 66, in _doValidation
ValueError: Unable to validate config file after upgrade: Key reportLineIndentation : the value "False" is of the wrong type.
Full result: (value of false means the key was not present)
[(['documentFormatting'], 'reportLineIndentation', VdtTypeError('the value "False" is of the wrong type.'))]

fullLog.txt
Configuration_file_after_reset.txt
Configuration_file_before_upgrade.txt

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

alpha-27213

Windows version:

Windows 10 22H2 (x64) build 19045.2251

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

None

Other information about your system:

None

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.

None

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

not tested

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

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions