[nvda] Re: Unable to get NVDA to load nvda.log

INFO - nvda (18:10:57):
Starting NVDA
INFO - core.main (18:10:57):
Config dir: C:\Documents and Settings\Administrator\Application Data\nvda
CRITICAL - nvda (18:10:57):
core failure
Traceback (most recent call last):
  File "nvda.pyw", line 111, in <module>
  File "core.pyc", line 65, in main
  File "config\__init__.pyc", line 142, in load
  File "configobj.pyc", line 1272, in __init__
  File "configobj.pyc", line 1341, in _load
  File "configobj.pyc", line 1637, in _parse
  File "configobj.pyc", line 1745, in _handle_error
  File "configobj.pyc", line 256, in __init__
  File "warnings.pyc", line 29, in _show_warning
  File "logHandler.pyc", line 135, in write
  File "logging\__init__.pyc", line 1084, in log
  File "logHandler.pyc", line 86, in _log
  File "logging\__init__.pyc", line 1129, in _log
  File "logging\__init__.pyc", line 1139, in handle
  File "logging\__init__.pyc", line 1176, in callHandlers
  File "logHandler.pyc", line 112, in handle
  File "nvwave.pyc", line 311, in playWaveFile
TypeError: 'NoneType' object is unsubscriptable

On 31/05/2009 5:29 p.m., Michael Curran wrote:

Hi,
I Think your NVDA config file is a bit mucked up. We would really like to solve this issue, as its happened to a few people.
Could you please send me your nvda log file, after trying to run your installed copy of NVDA?
It can be found by typing %temp% in the Windows explorer address bar and then pressing enter. (Include the percent signs). 
nvda.log should be in that directory.
Note that NVDA overrides this file all the time so you will have to use another screen reader such as narrator to retreave the file straight after the installed NVDA has terminated.
It would also be useful if you could send along your NVDA config file, which can be found in the nvda directory inside your user application data directory.
Try typing %appdata%\nvda in the Windows explorer address bar and then pressing enter. nvda.ini should be in that directory.
After sending nvda.log and nvda.ini via email, you can try deleting nvda.ini, and hopefully your newly installed NVDA should function correctly again ... if the problem is in deed the one I think it is.
However, for us to solve this problem for the future, we really need to see both the log file and the config file if that is possible.
I admit trying to find all these files is a bit of work, we may consider trying to improve this in the near future. 

Thanks
Mick




Or on Vista:



On 31/05/2009 3:03 PM, hurrikenny wrote:
INFO - nvda (18:10:57):
Starting NVDA
INFO - core.main (18:10:57):
Config dir: C:\Documents and Settings\Administrator\Application Data\nvda
CRITICAL - nvda (18:10:57):
core failure
Traceback (most recent call last):
  File "nvda.pyw", line 111, in <module>
  File "core.pyc", line 65, in main
  File "config\__init__.pyc", line 142, in load
  File "configobj.pyc", line 1272, in __init__
  File "configobj.pyc", line 1341, in _load
  File "configobj.pyc", line 1637, in _parse
  File "configobj.pyc", line 1745, in _handle_error
  File "configobj.pyc", line 256, in __init__
  File "warnings.pyc", line 29, in _show_warning
  File "logHandler.pyc", line 135, in write
  File "logging\__init__.pyc", line 1084, in log
  File "logHandler.pyc", line 86, in _log
  File "logging\__init__.pyc", line 1129, in _log
  File "logging\__init__.pyc", line 1139, in handle
  File "logging\__init__.pyc", line 1176, in callHandlers
  File "logHandler.pyc", line 112, in handle
  File "nvwave.pyc", line 311, in playWaveFile
TypeError: 'NoneType' object is unsubscriptable
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: 
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.12.46/2144 - Release Date: 05/30/09 
17:53:00

Other related posts: