Closed hwf1324 closed 2 months ago
cc @seanbudd
Before this, users had already reported this issue during the RC and Beta stages. At that time, these users were not utilizing the NVDA Chinese community mirror service. We did not pay much attention to the problem initially because the users were unable to provide specific reproduction steps or logs for analysis. The issue became more apparent when the NVDA Chinese community mirror service traffic was exhausted. A large number of users in the NVDA Chinese community reported that NVDA stopped working after updating to version 2024.3.
This issue might warrant a higher priority. We are currently advising users to temporarily disable add-on update notifications.
@seanbudd Perhaps the check should be run on the daemon thread, and should trigger an extensionPoint to fire the GUI portion once it is known whether there are updates?
cc @SaschaCowley
Can you please test this PR and see if it works as expected: https://ci.appveyor.com/api/buildjobs/pnr3dy4800nq6993/artifacts/output%2Fnvda_snapshot_try-fixAddonUpdateBG-33534%2C09eaf81e.exe
I reproduced the environment by redirecting nvaccess.org to 127.0.0.1 in the Host file.
From testing so far, this Issue seems to be resolved.
Hello,
CC @seanbudd I noticed this was merged into 2024.3.1 Will we consider releasing this version?
Yes - we were just waiting for alpha/beta testing. 2024.3.1 will be released next monday
Recently, a large number of users encountered this problem after upgrading to 2024.3 because the Chinese community mirror server ran out of traffic. I think this is the same for not being able to access the NV Access server.
Steps to reproduce:
Actual behavior:
When connecting to the server during a timeout. Unable to operate the computer, NVDA is blocked.
Expected behavior:
Does not block NVDA
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
install/portable
NVDA version:
2024.3 and versions with updated add-on notifications
Windows version:
Windows 11 Version 22H2 (OS internal version 22621.4037)
Name and version of other software in use when reproducing the issue:
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
yes
If NVDA add-ons are disabled, is your problem still occurring?
yes, it should also work for cases where you can't access the NV Access server.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
yes