-
-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NVDA stops reading webpages in all browser - saying "unknown" or "pane" #2807
Comments
Comment 1 by techczech on 2012-11-18 18:53
|
Comment 2 by briang1 on 2012-11-20 08:59 |
Comment 3 by techczech on 2012-11-25 11:35 But I did notice that it does not read PDFs - either in Adobe Reader XI or in PDF X-Change Viewer. It reads the interfaces but says 'avenue page view' when I mouse over the text pane but nothing else when I try to select text. As I said, it used to work on this machine. The problem is that I can't identify exactly what might have happened between it working and not working because I only use NVDA seldom for testing websites and I also test a lot of software. Could this be some sort of keylogger or other root malware on my machine? What kind of process would cause this? |
Comment 4 by mdcurran on 2012-11-26 08:04 |
Comment 5 by briang1 on 2012-11-26 18:18 |
Comment 6 by techczech on 2012-11-26 20:27 I tried the trial of JAWS13 and that works fine (so I'm assuming they use a different method). |
Comment 7 by jteh on 2012-11-26 21:22
|
Comment 8 by techczech on 2012-11-26 22:00 |
Comment 9 by briang1 on 2012-12-05 08:12 |
Comment 10 by jteh on 2012-12-05 08:25 |
Comment 11 by jteh (in reply to comment 8) on 2013-01-23 01:33
Can you please try the following?
|
Comment 13 by bgaraventa on 2014-09-10 23:25 I'm using a Win7 64bt machine new as of six months ago, and at first NVDA ran as expected. I remember checking a web page at the end of July, which worked fine, then have updated NVDA since then with newer versions, and now I can't access any web content in any browser. The browser opens, but it is impossible to navigate into and read the content. The rest of the OS appears to be accessible as before, just that all web content is now unreadable. I did all of the recommended steps above, and registered all of the DLLs successfully, restarted, and had the same result, then I ran the check cmd prompt indicated after, and got the following message: "Windows Resource Protection did not find any integrity violations." I restarted NVDA, with the same result. I uninstalled NVDA all together, erased any remaining files in %appdata% to clear everything, reinstalled the latest NVDA release as of today, and still have the same problem. Any ideas would be appreciated. |
Comment 14 by jteh on 2014-09-10 23:30 |
Comment 15 by briang1 on 2014-09-11 08:21 |
I am having this problem as well. This machine is a Windows 10 laptop, and I have been using NVDA with Firefox almost daily since January without problems. It came with Windows 10 Home from the factory, so this was not an upgrade. The problem started on last Thursday 5/12. I believe that it also coincided with a Windows update. But I have uninstalled all updates from that date and a few days before, and the problem persists. NVDA works correctly on the desktop, Windows start menu, and most applications. MSN Money reads perfectly, and NVDA is working with Edge. But it fails to work with IE11, Thunderbird, Chrome and Firefox ever since this problem has started. As I move through these applications, NVDA reads 'unknown' for each element (Chrome, FF, Thunderbird) or in IE11 NVDA is silent. This is the case when NVDA is installed on the machine or I use the portable version (both 2016.1) This problem is not present using JAWS. I've tried booting into safe mode to test, but I get a message indicating that no wave device is available to play sound. Please let me know what you think and if there is any other info I can provide. |
This occurs when certain Windows components become unregistered for some reason or another. Unfortunately, it can be one of several components. Please try the suggestions provided in earlier comments on this issue. |
I have tried registering all the DLLs listed on this issue, but no luck. This includes: c:\windows\system32\oleaut32.dll I tried: "c:\program files\internet explorer\ieproxy.dll" + "c:\program files (x86)\internet explorer\ieproxy.dll" but got file not found. Are there any other files you could suggest? Perhaps there are additional needed components in Windows 10? |
I don't know which .dll file was the cause, but NVDA is working again in all browsers after running this in a cmd window as admin:
effectively re-registering all components in the system32 folder. Thanks for the lead! |
Well usually its something in Office that seems to muck this up and I can :-) bglists@blueyonder.co.uk
|
same to me |
Just reiterating that for 64-bit systems, the following (from an admin command prompt) did the trick: C:\Windows\SysWOW64 regsvr32 oleacc.dll |
If you are needing help, I am willing to explain how to do this, On 10/26/2016 11:03 AM, zahra21 wrote:
Websites: email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu |
Further findings regarding regsvr32 oleacc.dll:
In other words, this doesn't quite do what we want: it leaves the typelib marshaller when it shouldn't. That could mean we end up with a situation where 32 and 64 bit are using a different marshaller, which means breakage. So, we should tweak the registry ourselves for IAccessible. |
There is no such thing as coincidence: today I had this problem with MathPlayer. So I would be happy to work on some kind of tool (though I lack the appropriate background). |
@dkager commented on 3 Aug 2017, 23:44 GMT+10:
It'd be great if you could confirm whether this registry patch (rename to .reg) fixes the issue. This is for a 64 bit system. If you're using a32 bit system, remove the sections containing WOW6432Node. |
For anyone experiencing this issue, please try the following. Note that these instructions are not as complete for Windows 8 and 8.1 yet.
|
Confirmed working, after restarting NVDA and Explorer. |
In Windows 10, on some machines NVDA has been saying unknown or pane in all browsers (apart from Edge). If using a copy of Mozilla Thunderbird, and you try and tab through to get to the tree view (where the folders are) it basically says unknown. It doesn't do anything in Mozilla Thunderbird. You can't even get to the menus in Mozilla Firefox. NVDA says unknown in the running applications section. It will not speak any of the icons there. If the applications key is used, it will not speak any of the menus. Yet it will work in other programs but not quite correctly at times. Refer to a suggestion from May 19th that fixed the problem, but other people on the NVDA list are having the same problem. This sometimes may be after a Windows update or if Office is uninstalled. The log here is from an earlier version of NVDA, but have seen people using 2017.2 have the same problem. |
@NZGene, it'd be good if you can try the steps I suggested in #2807 (comment) on affected machines and report whether that fixes the issue for you. The eventual aim is to develop a tool to fix problems like this automatically and it'd be helpful to know whether our suspicions about the cause of the problem are correct. Thanks. |
Hi @jcsteh - I've also been having issues with NVDA and have just applied fixes suggested in your comment above. I can confirm that NVDA now works correctly in Win7 SP1 with FF57 and IE11. I've tried both NVDA 2017.3 and 2017.4. Might be an idea to make this fix more prominent on NVDA website? Maybe on https://www.nvaccess.org/help/ |
Yes if you have a fix for this might be worth an update to nvda stable too
with info. I gave up and went back to the old esr, though may well take up
Jamies idea of a portable version if I can figure out how to register two
dlls in different places with the same name that is.. gulp.
Brian
|
As mentioned by some users, oneCoreCommonProxyStub.dll cannot be registered again on windows 10. It does not export DllRegisterServer. The alternative would be to put the needed registry values for IServiceProvider in a .reg file and import it to the Registry. Interestingly, Windows 10 refuses to import the file. I'm guessing that now windows 10 is protecting some system interfaces from being tampered with... which is a good thing. Let us hope that Trusted Installer also cannot do this and thus the issue with IServiceProvider becoming unregistered or incorrectly registered is no longer possible on windows 10. Note that even if trusted installer can do this, NVDA can never gain this permission, so we won't be able to fix it anyway. |
On windows 8.1, IServiceProvider is in actxprxy.dll. |
Hi- I am getting this error when I am trying trying to run the above command. Please if you can help! looking forward to hear back from you. |
@RadhikaTakyar |
Sorry about the inconvenience. Yes- error is to make sure that if the DLL is a valid DLL and asking to try again. So what can be done to reslove the issue. If the " alternative would be to put the needed registry values for IServiceProvider in a .reg file and import it to the Registry." also doesn’t work. |
This issue is now closed. Please open a new issue explaining what problem you are experiencing. Have you tried running COM Registration Fixing tool from the tools menu? |
Reported by techczech on 2012-11-18 17:48
Some time ago NVDA started to simply report "unknown" or "pane" when I try to read any webpage with it. I installed the 2012.3 beta and it started working but when I updated to the final version of 2012.3, it's happening again. This is an issue in Chrome, FF and IE 9. (Chrome and FF say "unknown" and IE9 says "pane").
I suspect it may be some problem with my computer (Win 7, 64bit, 8GB RAM, 128 SSD) since the same thing happens with portable versions that work on other machines but have no idea where to start looking.
Otherwise everything else seems to work fine. Even the Browser window (i.e. page title is read fine) but nothing on the webpage works.
I saw a similar issue reported on http://www.nvda-project.org/ticket/2624 but no resolution was offered.
I did notice that there were problems with pages that had not been fully loaded before but this is even on pages that are completely loaded.
Blocking #4408, #4641
The text was updated successfully, but these errors were encountered: