-
-
Notifications
You must be signed in to change notification settings - Fork 783
With a corrupted config file, NVDA restarts forever #15690
Copy link
Copy link
Closed
Labels
p2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
p2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Issue found while trying to improve corrupted config debugging.
Steps to reproduce:
Actual behavior:
NVDA restarts forever.
Note: Control+alt+delete and reboot your computer or change user session to avoid it to restart forever.
Expected behavior:
Restore the behaviour of NVDA 2023.1, that is:
NVDA should display a message that the config is corrupted and reinitialize it to default.
Note: The goal of this issue is to fix the regression that has occurred in NVDA 2023.2. I think that there is another issue to improve the behaviour existing in NVDA 2023.1, i.e. do not throw away the config file, but I have not been able to find it.
NVDA logs, crash dumps and other attachments:
nvda-old.log
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
NVDA 2023.3rc2
Windows version:
Windows 10 22H2 (AMD64) build 19045.3570
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.
Bug also present in NVDA 2023.2.
NVDA 2023.1 is fine instead.
If NVDA add-ons are disabled, is your problem still occurring?
Not tested; unrelated.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested; unrelated.