1. nvda@nvda.groups.io
  2. Messages
   Date   
Re: addon updater

Shaun Everiss
 

Well interestingly enough while it works on my system at home the same
error is happening on my secondary system on the secondary network I
am on.
Granted the system hasn't had all the updates of yesterday so I didn't
use it but I have just completed that and am in the process of doing
that now.
However yeah who knows its up and down.

On 02/10/2021, Louise Pfau <lpfau@...> wrote:
Hi. I don’t have a github account. I just checked for updates manually for
both add-ons and NVDA itself, and I didn’t get any errors. I received
notifications that there were no available updates in both instances. I’m
using an installed copy of NVDA 2021.2.

Louise
Re: addon updater

Louise Pfau
 

Hi.  I don’t have a github account.  I just checked for updates manually for both add-ons and NVDA itself, and I didn’t get any errors.  I received notifications that there were no available updates in both instances.  I’m using an installed copy of NVDA 2021.2.
 
Louise

Quick Question About Layout Tables

Jujube
 

Hi everyone,

I'm just curious about something. What exactly are layout tables and how are they different from normal/regular tables? I've found them helpful for making some tabular info on the web more accessible, but I'm curious as to what they really are. Thanks.
Re: addon updater

Shaun Everiss
 

Well there were a lot more 2-3 days ago including yesterday.

However for me right now its a non issue but I will respond later today from my secondary location to see.

Of course thats not got all the updates so maybe as soon as I start that systemm its going to update, in fact since that system aint my own I can'g garantee that its allready updated the required stuff.

It seems the issue went away as fast as it came but it could come back, its done this once before.



On 2/10/2021 4:39 am, Joseph Lee wrote:

Hi,

Tracking as a major issue - I have asked add-ons community about this issue. We can't detect patterns here as it shows up on some systems but not others.

Cheers,

Joseph
Re: addon updater

Shaun Everiss
 

Hmmm, well not sure what can be done, for me here its working though admittedly there is a server lag so who knows.

If its certs there is probably not much that can be done except wait for the new ones to propergate.



On 2/10/2021 4:29 am, Brian Vogel wrote:
GitHub Issue Created:
Manual attempts to update NVDA, or NVDA Add-Ons, is throwing error messages
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: addon updater

Shaun Everiss
 

Hmmm my issue was with the current stable, but things work as expected now.

It could be a cert issue and I do have the latest windows 10 updates including optionals, chrome, and edge, etc and a bunch of other updates went on my deskyesterday, so there is no way to check if the certs did actually download but since I needed updated certs to get updates I would presume they did.

Of course it may depend on where you are.

For those in the uk, europe, us, australia and may be other countries close to datahubs maybe thats less time for certs to get to where they need to do.

At least for me the issue on my network has stopped though I will be checking the secondary today so it could always depend on where things are.

For those having an issue, you could try an ipconfig /flushdns on your end which will cause windows to have to refresh all records and maybe certs.

Its not going to happen instantly but it may help.

You could also power down your router, let it rest for a minute then power back up to force a refresh of records.

However who knows.

The system is supposed to ideally autoupdate certs or download as needed and you shouldn't have to fiddle about.




On 2/10/2021 4:14 am, Gene wrote:
I’ve done more checking and I found an odd thing.  I have recent portable copies of NVDA.  One of them gives a proper update message when I run the updater.  Another one generates the error message.  This is for updating NVDA itself.  I don’t know why this is or what others experience but there is some sort of problem.  Whether and how it is related to the add-on problem, I don’t know but since I found it, I’m reporting it. 
 
The portable copies I tested the update feature on are betas but that shouldn’t matter.  They are betas of different recent versions.
 
Gene
-----Original Message-----
Sent: Friday, October 01, 2021 10:05 AM
Subject: Re: [nvda] addon updater
 
On Fri, Oct 1, 2021 at 08:23 AM, Chris wrote:
the problem is via check for updates menu item in NVDA only
-
And let's be perfectly clear here, it's via the Check for add-on updates in the NVDA Tools submenu.  The way this reads, it sounds like the Check for update. . .  option in the NVDA Help submenu.

I get the error message when I try a manual check for add-on updates.  I do not know whether this message is real (as in there is an actual error occuring) or spurious, as sometimes exception logic for "normal errors" can get buggy and a true error message gets thrown when, in reality, there isn't one.

I need to go back through this whole topic to see if an issue ticket for Add-On Updater exists for this.  If not, I'll create one, as something's gone wrong.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: addon updater

Shaun Everiss
 

Well maybe its propergation of the new certs.

Not only does it still work but updates for nvda and nvda addons work now.

So you may have to wait for things to update themselves.




On 1/10/2021 10:20 pm, Dejan Ristic wrote:

Hi once again,


I've tried to open www.nvaccess.org with Firefox. It's worked. If I'm allowed to express my opinion, chrome-based browsers refuse to access the site complaining about a privacy error and a certificate that has expired.


Stay safe and take care,


Dejan

On 01/10/2021 09:56, Chris via groups.io wrote:

I would imagine that we wouldn’t be able to access the site in that case along with everybody else

 

But that doesnt seem to be the case as others are not having problems whilst others are

 

 

From: Sarah k Alawami
Sent: 30 September 2021 23:50
To: nvda@nvda.groups.io
Subject: Re: [nvda] addon updater

 

I know there was somethingn on google news today about https certificates etc that expired. Could this have happened with nvda's site, or anywhere else that could have an effect on what's going on?

Sarah Alawami, owner of TFFP. .

For more info go to our website. . to subscribe to the feed click here

Our discord is where you will know when we go live on youtube, twitch and odysee. Thanks Restream staff.

Videos of some of our podcasts can be found on odysee

You can support the podcast by subscribing via the tip jar. You will get early access episodes plus no adds. If you cannot do that, then leave a 5 star rating on our podcast using your podcast directory's rating system.

On 30 Sep 2021, at 13:46, Dejan Ristic wrote:

Hi from me,

 

Just to let you know that I'm unable to access the NV access site, nor am I able to do the add-on and/or NVDA updates.

 

Cheers,

 

Dejan

On 30/09/2021 22:33, Chris via groups.io wrote:

Not only get an error checking for addon updates, also checking for NVDA updates pops up the same error message

 

 

From: Joseph Lee
Sent: 30 September 2021 19:26
To: nvda@nvda.groups.io
Subject: Re: [nvda] addon updater

 

Hi,

The author of Add-on Updater himself (I) have experienced this once, and the workaround seems to be to visit addons.nvda-project.org website using your preferred web browser. If NV Access server was offline, chances are that folks would have reported problems with not only Add-on Updater, but NVDA update checks as well, affecting folks who do ask NVDA to check for updates every day. Since it doesn't affect everyone, chances are that the computer (more specifically, the operating system) might be assuming that the web trusts soon to expire security certificate without realizing that it isn't - connecting to websites flagged as secure (such as NV Access website) would inform Windows that the web is safer again.

Cheers,

Joseph

 

 

Virus-free. www.avast.com

 
Re: addon updater

Sarah k Alawami
 

I move we hold Joseph hostage. I'm joking of corse. He rocks! Wow!

Happy Friday all.

Sarah Alawami, owner of TFFP. .

For more info go to our website. . to subscribe to the feed click here

Our discord is where you will know when we go live on youtube, twitch and odysee. Thanks Restream staff.

Videos of some of our podcasts can be found on odysee

You can support the podcast by subscribing via the tip jar. You will get early access episodes plus no adds. If you cannot do that, then leave a 5 star rating on our podcast using your podcast directory's rating system.

On 1 Oct 2021, at 10:58, Richard Wells wrote:

Joseph: Your solution worked perfectly. Now, I need to go around and update all of my NVDA installations. I have several so it will take a while. I don't know about the rest of the community, but as for me, I don't think we should allow Joseph to go anywhere. 😉

On 10/1/2021 12:12 PM, Joseph Lee wrote:

Hi all,

A possible workaround found: looks like it might be indeed NVDA. The following suggested workaround is applicable for NVDA 2021.2 or older and/or if you are running alpha snapshots released earlier than August 12, 2021:

  1. Press Control+NVDA+Z to open Python Console.
  2. Type the following as exactly as shown:

import updateCheck; updateCheck._updateWindowsRootCertificates()

I will do my best to release an Add-on Updater update this weekend in hopes of resolving this situation - note that the update will be a manual one; if it works, I'll make it available to the rest of the community next week (even then, you must apply the update manually if you are impacted).

Cheers,

Joseph
Re: addon updater

Joseph Lee
 

Hi,

The root cause was discovered by Lukasz Golonka in August 2021 - it turns out NVDA was assuming the internals of certificate related errors was the same between Python 2 and 3 when in fact it wasn't. Among other things, the old assumption prevented people who have just clean installed Windows without connecting to the Internet from completing the NVDA update check process when connected online. This issue is resolved from NVDA side in upcoming 2021.3 release (alpha phase at the moment); it happens that Add-on Updater assumed the same regarding certificate error internals, so I'll be resolving this from the add-on side this weekend.

Cheers,

Joseph
Re: addon updater

Richard Wells
 

Joseph: Your solution worked perfectly. Now, I need to go around and update all of my NVDA installations. I have several so it will take a while. I don't know about the rest of the community, but as for me, I don't think we should allow Joseph to go anywhere. 😉

On 10/1/2021 12:12 PM, Joseph Lee wrote:

Hi all,

A possible workaround found: looks like it might be indeed NVDA. The following suggested workaround is applicable for NVDA 2021.2 or older and/or if you are running alpha snapshots released earlier than August 12, 2021:

  1. Press Control+NVDA+Z to open Python Console.
  2. Type the following as exactly as shown:

import updateCheck; updateCheck._updateWindowsRootCertificates()

I will do my best to release an Add-on Updater update this weekend in hopes of resolving this situation - note that the update will be a manual one; if it works, I'll make it available to the rest of the community next week (even then, you must apply the update manually if you are impacted).

Cheers,

Joseph
Re: addon updater

Clement Chou
 

Yup. Unfortunately, still the same thing happening here. Running
windows 10 with NVDA version 2021.2.

On 10/1/21, Joseph Lee <joseph.lee22590@...> wrote:
Hi all,

According to an NVDA code contributor, this issue should be resolved in
alpha builds (2021.3 unless NV Access decides to backport this sooner). I'll
do something about this issue from Add-on Updater side if possible.

Cheers,

Joseph
Re: addon updater

Sam Bushman
 

That worked perfectly for me.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Friday, October 1, 2021 11:12 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] addon updater

 

Hi all,

A possible workaround found: looks like it might be indeed NVDA. The following suggested workaround is applicable for NVDA 2021.2 or older and/or if you are running alpha snapshots released earlier than August 12, 2021:

  1. Press Control+NVDA+Z to open Python Console.
  2. Type the following as exactly as shown:

import updateCheck; updateCheck._updateWindowsRootCertificates()

I will do my best to release an Add-on Updater update this weekend in hopes of resolving this situation - note that the update will be a manual one; if it works, I'll make it available to the rest of the community next week (even then, you must apply the update manually if you are impacted).

Cheers,

Joseph
Re: addon updater

Joseph Lee
 

Hi all,

A possible workaround found: looks like it might be indeed NVDA. The following suggested workaround is applicable for NVDA 2021.2 or older and/or if you are running alpha snapshots released earlier than August 12, 2021:

  1. Press Control+NVDA+Z to open Python Console.
  2. Type the following as exactly as shown:

import updateCheck; updateCheck._updateWindowsRootCertificates()

I will do my best to release an Add-on Updater update this weekend in hopes of resolving this situation - note that the update will be a manual one; if it works, I'll make it available to the rest of the community next week (even then, you must apply the update manually if you are impacted).

Cheers,

Joseph
Re: addon updater

Don H
 

Neither the update addon's under the tool menu of the NVDA UI nor the check for updates under the help menu work for me on my Win 10 system running latest version of NVDA.

On 10/1/2021 10:39 AM, Joseph Lee wrote:
Hi,
Tracking as a major issue - I have asked add-ons community about this issue. We can't detect patterns here as it shows up on some systems but not others.
Cheers,
Joseph
Re: addon updater

Joseph Lee
 

Hi all,

According to an NVDA code contributor, this issue should be resolved in alpha builds (2021.3 unless NV Access decides to backport this sooner). I'll do something about this issue from Add-on Updater side if possible.

Cheers,

Joseph
Re: addon updater

Sarah k Alawami
 

Not necessarily. When this certificate expired yesterday some sights were not affected but softwares were. I speak from experience as yesterday I was having loads of issues, luckelly not at work, at least, not yet.

Sarah Alawami, owner of TFFP. .

For more info go to our website. . to subscribe to the feed click here

Our discord is where you will know when we go live on youtube, twitch and odysee. Thanks Restream staff.

Videos of some of our podcasts can be found on odysee

You can support the podcast by subscribing via the tip jar. You will get early access episodes plus no adds. If you cannot do that, then leave a 5 star rating on our podcast using your podcast directory's rating system.

On 1 Oct 2021, at 0:56, Chris via groups.io wrote:

I would imagine that we wouldn’t be able to access the site in that case along with everybody else

 

But that doesnt seem to be the case as others are not having problems whilst others are

 

 

From: Sarah k Alawami
Sent: 30 September 2021 23:50
To: nvda@nvda.groups.io
Subject: Re: [nvda] addon updater

 

I know there was somethingn on google news today about https certificates etc that expired. Could this have happened with nvda's site, or anywhere else that could have an effect on what's going on?

Sarah Alawami, owner of TFFP. .

For more info go to our website. . to subscribe to the feed click here

Our discord is where you will know when we go live on youtube, twitch and odysee. Thanks Restream staff.

Videos of some of our podcasts can be found on odysee

You can support the podcast by subscribing via the tip jar. You will get early access episodes plus no adds. If you cannot do that, then leave a 5 star rating on our podcast using your podcast directory's rating system.

On 30 Sep 2021, at 13:46, Dejan Ristic wrote:

Hi from me,

 

Just to let you know that I'm unable to access the NV access site, nor am I able to do the add-on and/or NVDA updates.

 

Cheers,

 

Dejan

On 30/09/2021 22:33, Chris via groups.io wrote:

Not only get an error checking for addon updates, also checking for NVDA updates pops up the same error message

 

 

From: Joseph Lee
Sent: 30 September 2021 19:26
To: nvda@nvda.groups.io
Subject: Re: [nvda] addon updater

 

Hi,

The author of Add-on Updater himself (I) have experienced this once, and the workaround seems to be to visit addons.nvda-project.org website using your preferred web browser. If NV Access server was offline, chances are that folks would have reported problems with not only Add-on Updater, but NVDA update checks as well, affecting folks who do ask NVDA to check for updates every day. Since it doesn't affect everyone, chances are that the computer (more specifically, the operating system) might be assuming that the web trusts soon to expire security certificate without realizing that it isn't - connecting to websites flagged as secure (such as NV Access website) would inform Windows that the web is safer again.

Cheers,

Joseph

 

 

Virus-free. www.avast.com

 
Re: addon updater

Brian Vogel
 

Chris,

If you happen to have a GitHub account, and could do as Joseph asked and snag logs from your machine when it's working, and add a comment and attach those, it might help.

I just did this on my machine, which is failing for both of those update options.  Having a "compare and contrast" log data set could be useful.

I've been asked to test with an alpha build which, if necessary, I can easily do.  It won't be the first time.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: addon updater

Chris
 

Its both in the nvda help menu check for nvda update and the tools menu check for addon updates

 

Currently I can check for both addon updates and nvda update without an error

 

And others have found the same , it sometimes works but more often than not it does not

 

 

From: Brian Vogel
Sent: 01 October 2021 16:05
To: nvda@nvda.groups.io
Subject: Re: [nvda] addon updater

 

On Fri, Oct 1, 2021 at 08:23 AM, Chris wrote:

the problem is via check for updates menu item in NVDA only

-
And let's be perfectly clear here, it's via the Check for add-on updates in the NVDA Tools submenu.  The way this reads, it sounds like the Check for update. . .  option in the NVDA Help submenu.

I get the error message when I try a manual check for add-on updates.  I do not know whether this message is real (as in there is an actual error occuring) or spurious, as sometimes exception logic for "normal errors" can get buggy and a true error message gets thrown when, in reality, there isn't one.

I need to go back through this whole topic to see if an issue ticket for Add-On Updater exists for this.  If not, I'll create one, as something's gone wrong.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 

 
Re: addon updater

Joseph Lee
 

Hi,

Also, if possible, please attach log fragments to the GitHub issue just created. For best results, do:

  1. See if you do receive error messages when you check for NVDA and/or add-on updates.
  2. Restart with debug logging enabled.
  3. Repeat step 1.
  4. As soon as you receive the error message, press NVDA+F1 to open log viewer, select everything, copy the entire log to a new file and save it, then attach the file as a GitHub comment (not here please because debug logs can contain private information).

Cheers,

Joseph
Re: addon updater

Brian Vogel
 

On Fri, Oct 1, 2021 at 11:39 AM, Joseph Lee wrote:
We can't detect patterns here as it shows up on some systems but not others.
-
To the group membership:  Note the above well.  This is an example where adding comments to a ticket giving additional information about occurrences of this behavior will probably be pivotal to figuring out the root cause.

Just adding a comment noting whether you're using installed versus portable NVDA, what version, and what Windows version (and build, if applicable) would likely be helpful.  If you were to be happening to get an error message different than either of those I've documented here in this topic, which are repeated in that issue, that would be critical information, too, but I really doubt that anyone is getting something other than one of those two error messages based on what's been reported here.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
10301 - 10320 of 98297