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
Error when saving configuration #13187
Milestone
Comments
I don't think this is a regression, certainly something to fix though.
|
This was referenced Feb 14, 2023
Open
6 tasks
seanbudd
pushed a commit
that referenced
this issue
May 3, 2023
Fixes #13187 Summary of the issue: After having modified a parameter in a profile and then reset it to its original value with NVDA+control+C, it was not possible to save the configuration with NVDA+control+R; NVDA was complaining that the file system was probably read-only. Description of user facing changes NVDA will no longer refuse to save the configuration after a configuration reset. Description of development approach Bugfix: when resetting the config, config.conf._dirtyProfiles is cleared I have also narrowed the exception filtering when saving the config since in #13187, we get a message related to file write error, whereas the real error had nothing to do with it: it was a KeyError when trying to find "notepad" in config.conf._profileCache. I have filtered on PermissionError which is the error that I get when I set nvda.ini (or the whole NVDA setting folder) as read-only and try to save the config.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
Actual behavior:
A dialog appears with the following message:
"Cannot save configuration - file system is probably write protected"
Expected behavior:
No error message and configuration saved correctly.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2021.3.1
Windows version:
Windows 10 2004 (x64) build 19041.388
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.
No
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 tested
Here is the log:
log.txt
The text was updated successfully, but these errors were encountered: