Unable to update NVDA to 2019.2.1 #10311
Labels
p2
https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Comments
|
I can confirm this is the same here on my portable and installed version of
the latest beta.
It looks like the server is saying something weird, but then I'd have
thought such an error might be handled by the code in nvda?
INFO - __main__ (10:39:47.334):
Starting NVDA
INFO - core.main (10:39:47.536):
Config dir: C:\nvda full release\userConfig
INFO - config.ConfigManager._loadConfig (10:39:47.536):
Loading config: .\userConfig\nvda.ini
INFO - config.ConfigManager._loadConfig (10:39:47.552):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{u'schemaVersion': u'2', u'upgrade': {}, u'update': {u'autoCheck': u'False',
u'startupNotification': u'True', u'allowUsageStats': u'True',
u'askedAllowUsageStats': u'True'}, u'general': {u'language': u'Windows',
u'saveConfigurationOnExit': u'True', u'askToExit': u'True',
u'playStartAndExitSounds': u'True', u'loggingLevel': u'DEBUG',
u'showWelcomeDialogAtStartup': u'False'}, u'speech': {u'synth': u'espeak',
u'outputDevice': u'Speakers (4- BEHRINGER USB WDM ', u'symbolLevel': u'300',
u'espeak': {u'voice': u'en', u'variant': u'quincy', u'rate': u'40',
u'pitch': u'40', u'inflection': u'75', u'volume': u'87', u'capPitchChange':
u'46'}, u'mssp': {u'voice':
u'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech
Server\\v11.0\\Voices\\Tokens\\TTS_MS_en-GB_Hazel_11.0', u'volume': u'94',
u'rate': u'60'}, u'sapi5': {u'voice':
u'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\ScanSoftDaniel_Full_22kHz',
u'volume': u'88', u'rate': u'60'}, u'sapi4': {u'voice':
u'{BF5EAD40-9F65-11CF-8FC8-0020AF14F271}', u'rate': u'57', u'pitch': u'20',
u'volume': u'50'}, u'dectalk': {u'voice': u'Dennis', u'rate': u'50',
u'pitch': u'17', u'inflection': u'40'}, u'speechPlayerInEspeak': {u'voice':
u'en', u'variant': u'quincy', u'rate': u'46', u'pitch': u'40',
u'inflection': u'75', u'volume': u'88'}, u'pico': {u'voice': u'en-gb',
u'volume': u'73', u'rate': u'54'}}, u'braille': {u'noBraille': {u'port':
u''}}, u'mouse': {u'reportObjectRoleOnMouseEnter': u'True'},
u'presentation': {u'reportTooltips': u'True',
u'guessObjectPositionInformationWhenUnavailable': u'True',
u'progressBarUpdates': {u'progressBarOutputMode': u'both'}},
u'virtualBuffers': {u'autoPassThroughOnCaretMove': u'True',
u'autoPassThroughOnFocusChange': u'True'}, u'documentFormatting':
{u'reportAlignment': u'True', u'reportSpellingErrors': u'True',
u'reportLineIndentation': u'False', u'reportBlockQuotes': u'False',
u'autoLanguageSwitching': u'True', u'reportLineIndentationWithTones':
u'True'}, u'clipContentsDesigner': {u'confirmToCopy': u'True',
u'confirmToCut': u'True'}, u'development': {}}
DEBUG - core.main (10:39:47.568):
setting language to Windows
INFO - core.main (10:39:47.568):
NVDA version 2019.2.1beta1
INFO - core.main (10:39:47.568):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (10:39:47.568):
Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC
v.1500 32 bit (Intel)]
INFO - core.main (10:39:47.568):
Using comtypes version 1.1.7
INFO - core.main (10:39:47.568):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUG - core.main (10:39:47.611):
Initializing add-ons system
snip
IO - speech.speak (10:40:18.078):
Speaking [LangChangeCommand ('en_GB'), u'Not now Alt+n']
IO - inputCore.InputManager.executeGesture (10:40:18.773):
Input: kb(desktop):enter
ERROR - unhandled exception (10:40:18.776):
Traceback (most recent call last):
File "updateCheck.pyo", line 733, in onClose
File "updateCheck.pyo", line 417, in _download
File "updateCheck.pyo", line 553, in __init__
KeyError: 'apiVersion'
This on a portable version.
Brian
bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
|
|
Thanks for the report, we'll look into this with urgency. |
feerrenrut
added
the
p2
|
Either this has already been fixed on the update server side, or the updateInfo sent to 2019.2 stable users is not the same: Update works fine here from 2019.2 stable. |
|
JulienCochuyt commented 10 minutes ago
For me the issue is not fixed at this moment. |
|
This is only affecting beta users. I'm looking into this now. |
|
Update server now provides the missing keys (apiVersion and apiCompatTo) when redirecting updates to 2019.2.1 if older than 2019.1, and it now correctly parses beta version strings, which were previously being treated as being older than 2019.1. |
|
michaelDCurran commented 17 minutes ago
This fixes the issue for me. Thanks! I think we can close the issue. I will do now. |
|
Its worked on the RC, but i have one beta that says there are no updates.
NVDA version beta-18478,0887269f
INFO - core.main (16:20:00.111):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (16:20:00.111):
Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC
v.1500 32 bit (Intel)]
INFO - core.main (16:20:00.111):
Using comtypes version 1.1.7
INFO - core.main (16:20:00.111):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUG - core.main (16:20:00.111):
Maybe its too old?
Brian
bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
-----
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please thoroughly read NVDA's wiki article on how to fill in this template, including how to provide the required files.
Issues may be closed if the required information is not present.
https://github.com/nvaccess/nvda/wiki/Github-issue-template-explanation-and-examples
-->
Steps to reproduce:
Actual behavior:
The update is not downloaded and the log shows this error:
Expected behavior:
The update should be downloaded and installed.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2019.2.1beta1
Windows version:
7 and 10
Name and version of other software in use when reproducing the issue:
n/a
Other information about your system:
Tested with add-ons disabled.
Other questions
Does the issue still occur after restarting your PC?
Yes.
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes, NVDA 2019.2.2rc1 (not available now).
The text was updated successfully, but these errors were encountered: