Cannot save the configuration file #114

Closed
nvaccessAuto opened this Issue Jan 1, 2010 · 10 comments

2 participants

@nvaccessAuto

Reported by katsutoshi on 2008-06-18 02:52
With latest snapshot, I can not save the configuration file(nvda.ini) with Japanese Windows.

Steps to Reproduce

  1. Download the latest snapshot from NVDA Snapshot page(I tried with both installer and zip file).
  2. Run the NVDA and change synthesizer from eSpeak to SAPI4 Active voice.
  3. Press Nvda+Ctrl+C or use NVDA menu to save settings.

Result

I got a message "Could not save configuration - probably read only file system". And if I restart NVDA, it was started with eSpeak.
But, if I work with source code of NVDA, this problem doesn't happen.

Answers to Jamie's questions

  • What revision of NVDA is this?

I tested with nvda_snapshot_trunk-r2136.

  • Are you testing with official pre-built snapshots?

Yes. It was from official snapshot page.

  • What operating system(s)?

I tested with 3 Windows XP with SP3 installed machines and 1 Windows Vista with SP1 installed machine. All of them are Japanese version.
Now, I am asking NVDA Japanese translate team to test this problem with their machines. When I get messages from them, I'll report them.

  • Is NVDA running as a normal user or as administrator?

I tested with administrator users.

  • Does this happen for other Japanese users also?

Yes. My coworkers machine also had same problem. But, I am still correcting the data from testers.

  • Does this work properly for you in earlier versions of NVDA?

Yes.
In my computer, I have division2057 and I couldn't find problem like this with 2057.

@nvaccessAuto

Attachment nvda.log added by katsutoshi on 2008-07-09 03:31
Description:

@nvaccessAuto

Attachment nvda.2.log added by katsutoshi on 2008-07-09 04:34
Description:
Tested with log level DEBUGWARNING

@nvaccessAuto

Comment 1 by jteh on 2008-06-21 00:51
Reporter has identified that this regressed in r2070.

@nvaccessAuto

Comment 2 by jteh on 2008-07-08 11:51
This may be fixed in r2204. Please test and report.

@nvaccessAuto

Comment 3 by katsutoshi on 2008-07-09 03:36
I tested with latest trunk version r2205 and got same error message.
I hope nvda.log which I attached help you to find the problem.

@nvaccessAuto

Comment 4 by jteh on 2008-07-09 03:47
Please set your log level to DEBUGWARNING in NVDA->Preferences->General, repeat the test and attach this log file.

@nvaccessAuto

Comment 5 by katsutoshi (in reply to comment 4) on 2008-07-09 04:35
Replying to jteh:

Please set your log level to DEBUGWARNING in NVDA->Preferences->General, repeat the test and attach this log file.

I tested with log level DEBUGWARNING. I'll reattach nvda.log file.

@nvaccessAuto

Comment 6 by jteh on 2008-07-09 10:15
Ack. It seems that my suspicion was right, but my fix didn't quite fix the entire problem. I know what needs to be done, but it is a litle more complicated than initially suspected.
Changes:
Milestone changed from 0.6 to 0.6p2

@nvaccessAuto

Comment 7 by jteh on 2008-07-09 11:31
Hopefully fixed by r2206. Please tst and report. Note that this requires MiscellaneousDependencies 2008-07-09-01. Also, please remove config/*.pyc to be sure. This will be in snapshots from r2206.

@nvaccessAuto

Comment 8 by katsutoshi (in reply to comment 7) on 2008-07-10 01:15
Replying to jteh:

Hopefully fixed by r2206. Please tst and report. Note that this requires MiscellaneousDependencies 2008-07-09-01. Also, please remove config/*.pyc to be sure. This will be in snapshots from r2206.

I tested latest version and it works fine now.
I can save configuration file after I changed some settings.
Thank you for your great work.

Changes:
State: closed

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015
@jcsteh jcsteh was assigned by nvaccessAuto Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 0.6p2 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment