errors I get? don't understand.


 

A gentle reminder about posting logs or log segments:  Please don't.

Group administration has asked, on multiple occasions, that full logs and log segments not be posted to the group.  There are very good reasons for this, including protecting the privacy of the member whose log material may contain information that would be considered private.

We ask that you note that you have a log or log segment available for review if an assistant wishes to see it, and that said materials be shared privately, not on the group.  Anyone who is capable of interpreting logs who wants to see one will ask if such is needed to figure out what's happening.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard


Brian's Mail list account
 

Ah, possibly part of the issue, but you need to keep an eie on the system as boot up issues can be very flaky at times.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Curtis Delzer" <curtis@...>
To: <nvda@nvda.groups.io>
Sent: Saturday, August 13, 2022 6:31 AM
Subject: [nvda] fixed it.


My errors; I deleted the configuration folder under "roaming," and it was very large, so due to it probably having old stuff in it, (which hadn't been deleted), (among other things) all is ok now, no more errors.

Funny, though in versions earlier than this current beta, no error sounds came up but the same or similar errors were generated in the log.

I just wasn't apprised of them because there wasn't any error sounds until this beta gave me plenty of them.

--
Curtis Delzer
H.S.
K6VFO
Rialto, CA
curtis@...





Brian's Mail list account
 

Yes that was part of my deduction. I think they should obliterate the current install, and start afresh with no add ons at all and allow it to use whatever it defaults to. Normally either 1 core or Espeak. If neither come up look at the log with a portable copy or narrator and look to see if the system sees sound hardware. As I say, I have known occasions where the sound drivers were not initialised when NVDA looks for audio devices, it then sets sound to silence.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gene" <gsasner@...>
To: <nvda@nvda.groups.io>
Sent: Saturday, August 13, 2022 4:50 AM
Subject: Re: [nvda] errors I get? don't understand.


I wouldn't want to generalize but when I upgraded from one version of
NVDA to another, even with compatible add-ons, some of them didn't
work. Is it common for add-ons to need reinstalling when you create an
installed version from a portable version or upgrade?

You talked about a tripple talk problem. I'm not sure if that accounts
for NVDA appearing not to run because it should revert to the default
NVDA synthesizer if it can't run the assigned one but even so, it makes
me wonder if my suspicion was correct yesterday, that the screen-reader
could be running without speech.

Gene

On 8/12/2022 9:55 PM, Joseph Lee wrote:

Hi,

These are add-on errors. Specifically:

1. TripleTalk USB: an issue with the add-on manifest.
2. Conflict between NVDA Extension and Sound Splitter add-ons when
trying to initialize wave playback subsystem in NVDA.
3. Inability to access a specific web resource from an add-on.

When you do send log fragments (if you must do so), please only
include the fragment that results in errors (typically a fragment that
starts with "error" followed by timestamp and traceback). While the
info log does not contain input and output data, it still contains
enough information to figure out specs of your system and user path.

A tip for folks parsing NVDA logs: the log analyzed is one of those
that include tracebacks from add-ons. You can determine involvement of
add-ons in error messages if parts of the traceback refer to what
appears to be NVDA user configuration folder path, and that
probability increases if the error traceback does end with an error
coming from an add-on. I state the last sentence like this (increase
in probability) because:

1. Add-ons can and sometimes do patch NVDA screen reader itself in
predictable and unpredictable ways. This stems from not NVDA, but
due to Python internals. The fragment about an add-on saying that
another add-on patched parts of NVDA is a good example.
2. Add-ons can call NVDA features without realizing that it doesn't
exist or things have changed. This is the reason why just editing
the manifest will not work on all add-ons.

I think the log fragment posted indicates issues beyond NV Access's
control; no, actually these are issues beyond NVDA developers' control
as add-ons are involved in the log fragment, more so for this
fragment. I suggest contacting authors of affected add-ons (for Sound
Splitter, I have no plans to resolve this at this time as I'm no
longer maintaining it).

Cheers,

Joseph






Curtis Delzer
 

My errors;  I deleted the configuration folder under "roaming," and it was very large, so due to it probably having old stuff in it, (which hadn't been deleted), (among other things) all is ok now, no more errors.

Funny, though in versions earlier than this current beta, no error sounds came up but the same or similar errors were generated in the log.

I just wasn't apprised of them because there wasn't any error sounds until this beta gave me plenty of them.

--
Curtis Delzer
H.S.
K6VFO
Rialto, CA
curtis@...


 

Hi,

Even if an add-on advertises itself as compatible, it does not mean the actual add-on code was edited to use changes from NVDA itself. This is more so if a version of NVDA introduced changes that can break certain add-ons, most notably speech synthesizer add-ons, made complicated if something (a different add-on, perhaps) other than these made internal changes to (patched) NVDA that renders some synthesizers inoperable or fail to load properly.

As for add-ons and installing NVDA from portable versions: yes if the user checked "copy portable user configuration" checkbox. If one or more incompatible add-ons are detected, users might be asked to review them.

As for running NVDA with or without speech: yes, it is possible to run NVDA without speech. Speaking of speech syntehsizers, if an external speech synthesizer fails to load, NVDA will resort to either eSpeak NG or Windows OneCore voices if running on Windows 7/8.x or Windows 10 and later, respectively.

Regarding TripleTalk issue, the log reports an issue with add-on manifest validation. This is because the add-on summary data is not formatted as a proper Python string. Without going into technical details (ask on NVDA add-ons list or me privately), if the add-on manifest data is not written correctly, Python (NOT NVDA) will recognize manifest data as something other than text. More specifically:

  • manifest = text1, text2: recognized by Python as a list, not text, fails add-on manifest validation.
  • manifest = "text1, text2": recognized by Python as text, add-on manifest is valid.

Cheers,

Joseph


Gene
 

I wouldn't want to generalize but when I upgraded from one version of NVDA to another, even with compatible add-ons, some of them didn't work.  Is it common for add-ons to need reinstalling when you create an installed version from a portable version or upgrade?

You talked about a tripple talk problem.  I'm not sure if that accounts for NVDA appearing not to run because it should revert to the default NVDA synthesizer if it can't run the assigned one but even so, it makes me wonder if my suspicion was correct yesterday, that the screen-reader could be running without speech.

Gene

On 8/12/2022 9:55 PM, Joseph Lee wrote:

Hi,

These are add-on errors. Specifically:

  1. TripleTalk USB: an issue with the add-on manifest.
  2. Conflict between NVDA Extension and Sound Splitter add-ons when trying to initialize wave playback subsystem in NVDA.
  3. Inability to access a specific web resource from an add-on.

When you do send log fragments (if you must do so), please only include the fragment that results in errors (typically a fragment that starts with "error" followed by timestamp and traceback). While the info log does not contain input and output data, it still contains enough information to figure out specs of your system and user path.

A tip for folks parsing NVDA logs: the log analyzed is one of those that include tracebacks from add-ons. You can determine involvement of add-ons in error messages if parts of the traceback refer to what appears to be NVDA user configuration folder path, and that probability increases if the error traceback does end with an error coming from an add-on. I state the last sentence like this (increase in probability) because:

  1. Add-ons can and sometimes do patch NVDA screen reader itself in predictable and unpredictable ways. This stems from not NVDA, but due to Python internals. The fragment about an add-on saying that another add-on patched parts of NVDA is a good example.
  2. Add-ons can call NVDA features without realizing that it doesn't exist or things have changed. This is the reason why just editing the manifest will not work on all add-ons.

I think the log fragment posted indicates issues beyond NV Access's control; no, actually these are issues beyond NVDA developers' control as add-ons are involved in the log fragment, more so for this fragment. I suggest contacting authors of affected add-ons (for Sound Splitter, I have no plans to resolve this at this time as I'm no longer maintaining it).

Cheers,

Joseph



 

Hi,

These are add-on errors. Specifically:

  1. TripleTalk USB: an issue with the add-on manifest.
  2. Conflict between NVDA Extension and Sound Splitter add-ons when trying to initialize wave playback subsystem in NVDA.
  3. Inability to access a specific web resource from an add-on.

When you do send log fragments (if you must do so), please only include the fragment that results in errors (typically a fragment that starts with "error" followed by timestamp and traceback). While the info log does not contain input and output data, it still contains enough information to figure out specs of your system and user path.

A tip for folks parsing NVDA logs: the log analyzed is one of those that include tracebacks from add-ons. You can determine involvement of add-ons in error messages if parts of the traceback refer to what appears to be NVDA user configuration folder path, and that probability increases if the error traceback does end with an error coming from an add-on. I state the last sentence like this (increase in probability) because:

  1. Add-ons can and sometimes do patch NVDA screen reader itself in predictable and unpredictable ways. This stems from not NVDA, but due to Python internals. The fragment about an add-on saying that another add-on patched parts of NVDA is a good example.
  2. Add-ons can call NVDA features without realizing that it doesn't exist or things have changed. This is the reason why just editing the manifest will not work on all add-ons.

I think the log fragment posted indicates issues beyond NV Access's control; no, actually these are issues beyond NVDA developers' control as add-ons are involved in the log fragment, more so for this fragment. I suggest contacting authors of affected add-ons (for Sound Splitter, I have no plans to resolve this at this time as I'm no longer maintaining it).

Cheers,

Joseph


Curtis Delzer
 

INFO - __main__ (18:49:18.081) - MainThread (12380):
Starting NVDA version 2022.3beta2
INFO - core.main (18:49:18.380) - MainThread (12380):
Config dir: C:\Users\admin\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:49:18.391) - MainThread (12380):
Loading config: C:\Users\admin\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:49:18.561) - MainThread (12380):
Windows version: Windows 10 21H2 (10.0.19044) workstation
INFO - core.main (18:49:18.561) - MainThread (12380):
Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)]
INFO - core.main (18:49:18.561) - MainThread (12380):
Using comtypes version 1.1.11
INFO - core.main (18:49:18.561) - MainThread (12380):
Using configobj version 5.1.0 with validate version 1.0.1
WARNING - addonHandler._report_manifest_errors (18:49:19.470) - MainThread (12380):
Error loading manifest:
{'name': True, 'summary': True, 'description': VdtTypeError('the value "[\'Basic support for the Tripletalk USB hardware speech synthesizer. Indexing is not functional\', \'and no voice support. This will be fixed in a future update.\']" is of the wrong type.'), 'author': True, 'version': True, 'minimumNVDAVersion': True, 'lastTestedNVDAVersion': True, 'url': True, 'docFileName': True}
ERROR - addonHandler._getAvailableAddonsFromPath (18:49:19.470) - MainThread (12380):
Error loading Addon from path: C:\Users\admin\AppData\Roaming\nvda\addons\ttusb
Traceback (most recent call last):
  File "addonHandler\__init__.pyc", line 209, in _getAvailableAddonsFromPath
  File "addonHandler\__init__.pyc", line 333, in __init__
addonHandler.AddonError: Manifest file has errors.
INFO - synthDriverHandler.setSynth (18:49:22.201) - MainThread (12380):
Loaded synthDriver ibmeci
WARNING - mathPres.initialize (18:49:22.211) - MainThread (12380):
MathPlayer 4 not available
INFO - core.main (18:49:22.311) - MainThread (12380):
Using wx version 4.1.1 msw (phoenix) wxWidgets 3.1.5 with six version 1.16.0
INFO - brailleInput.initialize (18:49:22.311) - MainThread (12380):
Braille input initialized
INFO - braille.initialize (18:49:22.311) - MainThread (12380):
Using liblouis version 3.22.0
INFO - braille.initialize (18:49:22.311) - MainThread (12380):
Using pySerial version 3.5
INFO - braille.BrailleHandler.setDisplayByName (18:49:22.321) - MainThread (12380):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleDisplayDrivers.freedomScientific.BrailleDisplayDriver.__init__ (18:49:22.381) - braille._BgThread (12928):
Found Focus 40 connected via custom (\\?\usb#vid_0f4e&pid_0114#0123456#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
INFO - braille.BrailleHandler.setDisplayByName (18:49:22.391) - braille._BgThread (12928):
Loaded braille display driver freedomScientific, current display has 40 cells.
INFO - core.main (18:49:22.573) - MainThread (12380):
Java Access Bridge support initialized
INFO - UIAHandler.UIAHandler.MTAThreadFunc (18:49:22.651) - UIAHandler.UIAHandler.MTAThread (8496):
UIAutomation: IUIAutomation6
INFO - config.ConfigManager._loadConfig (18:49:26.684) - MainThread (12380):
Loading config: C:\Users\admin\AppData\Roaming\nvda\profiles\reportPasswords.ini
INFO - external:globalPlugins.NVDAExtensionGlobalPlugin.theGlobalPlugin.NVDAExtensionGlobalPlugin.__init__ (18:49:27.392) - MainThread (12380):
Loaded NVDAExtensionGlobalPlugin version 11.2
WARNING - external:globalPlugins.NVDAExtensionGlobalPlugin.computerTools.volumeControl.getNVDAVolumeObj (18:49:27.453) - MainThread (12380):
NVDA volume object not found and cannot be initialized
ERROR - external:globalPlugins.NVDAExtensionGlobalPlugin.computerTools.volumeControl.initialize (18:49:27.453) - MainThread (12380):
Initialization failed: nvwave.WavePlayer.open already patched by: globalPlugins.soundSplitter
INFO - core.main (18:49:30.114) - MainThread (12380):
NVDA initialized
ERROR - unhandled exception (18:49:30.521) - MainThread (12380):
Traceback (most recent call last):
  File "wx\core.pyc", line 3407, in <lambda>
  File "C:\Users\admin\AppData\Roaming\nvda\addons\NAPS2TesseractOCR\globalPlugins\NAPS2TesseractOCR\update.py", line 88, in upgradeVerify
    r = urllib.request.urlopen(p).read()
  File "urllib\request.pyc", line 222, in urlopen
  File "urllib\request.pyc", line 531, in open
  File "urllib\request.pyc", line 641, in http_response
  File "urllib\request.pyc", line 569, in error
  File "urllib\request.pyc", line 503, in _call_chain
  File "urllib\request.pyc", line 649, in http_error_default
urllib.error.HTTPError: HTTP Error 404: Not Found
WARNING - external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncementAndRemanence.initialize (18:49:30.581) - MainThread (12380):
commandKeysSelectiveAnnouncementAndRemanence initialized
WARNING - external:globalPlugins.NVDAExtensionGlobalPlugin.speechHistory.initialize (18:49:30.591) - MainThread (12380):
speechHistory initialized

--
Curtis Delzer
H.S.
K6VFO
Rialto, CA
curtis@...