Date   

Re: multiple instances of NVDA

Quentin Christensen
 

Interesting, I regularly restart NVDA and I don't recall ever seeing it from that.  Do you have any add-ons?


On Fri, Aug 21, 2020 at 4:35 PM Luke Davis <luke@...> wrote:
On Fri, 21 Aug 2020, Quentin Christensen wrote:

> This is generally caused by something closing NVDA unexpectedly, such as it crashing, or if you go to task manager and "End task" it.  I haven't seen it
> when restarting or updating add-ons.  I wonder if it is a particular add-on which is not letting NVDA shut down cleanly?
> If anyone replicates this, ideally with the log set to debug level, I'd be interested in your nvda-old.log file (the one from when NVDA didn't shut down
> properly).

I'll get you one, but I must say that I have rarely NOT had this happen when
doing an NVDA restart.
It is just the way of things.
Since it happens on all of my systems, I assumed it was an error with slave or
helper, and couldn't be avoided.

Luke





--
Quentin Christensen
Training and Support Manager


Re: multiple instances of NVDA

Luke Davis
 

On Fri, 21 Aug 2020, Quentin Christensen wrote:

This is generally caused by something closing NVDA unexpectedly, such as it crashing, or if you go to task manager and "End task" it.  I haven't seen it
when restarting or updating add-ons.  I wonder if it is a particular add-on which is not letting NVDA shut down cleanly?
If anyone replicates this, ideally with the log set to debug level, I'd be interested in your nvda-old.log file (the one from when NVDA didn't shut down
properly).
I'll get you one, but I must say that I have rarely NOT had this happen when doing an NVDA restart.
It is just the way of things.
Since it happens on all of my systems, I assumed it was an error with slave or helper, and couldn't be avoided.

Luke


Re: I greet thee with a bug report

Gene
 

It may be that sending a log to those who have the technical knowledge to understand it might give an answer. I'll let those who know about the way to have the log contain the information you want and set the log to the correct level discuss the matter further.

Aside from that, if the log doesn't give a good answer you can implement, do you have system restore points? Can you run one from before the problem started? Sometimes, that's the best way to solve an obscure problem which might take a lot of time and effort to solve.

Gene

-----Original Message-----
From: Brandon Cole
Sent: Thursday, August 20, 2020 5:51 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I greet thee with a bug report



Thanks for this suggestion, but sadly it did not work. I ran the tool, restarted the whole system, and still have the same issue. Bah, I say. Bah.







From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Sent: Thursday, August 20, 2020 6:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I greet thee with a bug report





Hi



Try the following first it is found under the tools then the menu you want is called Run COM Registration Fixing tool...

Then follow the directions.



If you do not know how many times to get to those menus do the following if not spoken out.



nvda key + letter N to bring up the preferences menu then arrow down2 times this will put you on the tools menu there is a sub menuthen use the right arrow key to open the sub menu then arrow down 7 times this will put you on the com registration menu then press the enter key..



hopefully that fixes the problem for you. You might have to also reboot the pc for it to come right.



Gene nz







On 21/08/2020 9:46 am, Brandon Cole wrote:



Greetings,

I come seeking assistance with an NVDA bug that has recently sprung up. For some reason, NVDA will no longer read any of its own dialogs. The NVDA menu, the quit NVDA dialog, and so on. Furthermore, these dialogs no longer seem to have titles at all, let alone much content in them. Running NVDA whilst also running Jaws just to be sure showed me this. When bringing up the NVDA menu, NVDA said nothing at all, but even Jaws only said “submenu, submenu, submenu” as I browsed through the items. What’s more, anything that had an associated hot key didn’t seem to have one. Instead of saying Alt Plus T or Alt Plus B for example, what I heard was “Alt Plus…” And then simply nothing. I even uninstalled NVDA and reinstalled it, only to discover the issue persisted even during the reinstallation. It is a very disconcerting bug, and I am desperately hoping someone else has heard of this before. Thanks for any help you can provide. One final note for whatever it’s worth, this bug only seems to affect NVDA. Jaws is just fine.

Thanks all!


Re: lion universal subtitle reader and more NVDA addon

abdul muhamin
 

I hope you will find the solution soon, try this addon, I’m bet you can do it more better then this

 

Sent from Mail for Windows 10

 

From: Joseph Lee
Sent: Thursday, August 20, 2020 10:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] lion universal subtitle reader and more NVDA addon

 

Hi,

Suffice to say that someone (not me) is researching this possibility at the moment.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of abdul muhamin
Sent: Thursday, August 20, 2020 9:32 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] lion universal subtitle reader and more NVDA addon

 

Hi, I’m using this addon on win10 with the latest NVDA, the best thing of this addon is to read the subtitles and on screen text automatically. If possible, please add this functionality to NVDA core, so that it can be used with Win10 ocr.

 

Sent from Mail for Windows 10

 

From: Joseph Lee
Sent: Wednesday, August 19, 2020 8:32 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] lion subtitle reader and more addon

 

Hello everyone,

I took a look at this add-on, and I'm afraid this one isn't really compatible with recent NVDA releases and other issues were found (no wonder it is labeled a "beta" at this time). Specifically:

* OCR engine: it uses OCR engine found in Windows 10. Therefore unless you are using Windows 10, you won't be able to use this add-on at all (you can configure things, but the thing that enables this add-on is missing on older Windows releases).

* It uses code fragments that are no longer supported in newer NVDA dependencies (specifically, wxPython).

Thanks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Vaibhav Bhandari

Sent: Wednesday, August 19, 2020 8:17 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] lion subtitle reader and more addon

 

Hi,

You can download the addon from the link given below- https://blindieconnect.net/files/lion-latest.nvda-addon

 

On 8/19/20, Aravind R <aravind.andhrabank@...> wrote:

> add on link is not pasted boss.

> On 19/08/2020, Josh Kennedy <joshknnd1982@...> wrote:

>> Hi,

>> Here pasted below is the lion subtitle reader and more documentation.

>> My question though is, what is the very first combo box used for in

>> lion settings never mind I figured it out it changes how often OCR is

>> performed.

>> 

>> What is it

>> LION is an addon which does Automatic OCr of certain screen portions,

>> at a certain interval. Why do I say that it is intelligent? No, not

>> because I've written it, nor because the "i" makes for a nice

>> acronym. Since it does OCR of the same screen portion multiple times,

>> normally it would read the same text multiple times, which is not

>> very nice. So, I implemented a mechanism to skip speaking of the text

>> if it seems similar to the previously recognised text.

>> What can I do with it?

>> The main reason I wrote it was to read subtitles. Due to the way it

>> works, it can read any subtitles on the screen, including Youtube,

>> Netflix and other online video sites, subtitles embedded in AVI

>> files, and even live tV!

>> Make sure to set the video to full screen when using it, as it works

>> like sighted eyes do. It needs big text for better performance. The

>> quality won't be perfect, try to set the font of the subtitles as

>> large as possible, if you have the option, and use a high resolution

>> screen. The OCR engine it uses is not perfect. It may have inferior

>> results on certain images.

>> Other than that, It can be used to monitor any inaccessible text on

>> the screen, like video game menus. It won't tell you highlighted

>> text, unfortunately.

>> How do I use it?

>> To launch it with default options, just press NVDA+alt+l. LION will

>> start OCR of the whole screen at a 1 second interval, speaking only

>> when the text changes. Hopefully. :) If you want to customize its

>> behaviour, go to the NVDA Menu, Preferences, LION settings. For

>> example, a video file might have a logo in the upper left corner that

>> gets read along with the subtitle, and disrupts the experience. We'll

>> see how to fix this in the next section.

>> LION has the following settings:

>> 1. OCR interval: how often the program does OCR. Takes values from

>> 0.1 second to 10 seconds.

>> 2. OCR target: specifies the screen portion to OCR. Options are:

>> current control, current window, navigator object, and full screen 3.

>> Crop pixels from above, below, right, left. In full screen mode,

>> those four fields allow you to crop sections from the screen from

>> being scanned.

>> Those settings work only in full screen and current window modes.

>> Why is this setting useful? Let's remember the logo example above.

>> Just crop 10% or so from above to skip the logo, and you won't hear

>> it. Actually, to make the recognition faster and less resource

>> intensive, you can crop like 70% from above, since subtitles are

>> usually found in the lower third of the screen.

>> what's new

>> version 1.11

>> Fixed a bug, mainly observed in youtube fullscreen.

>> version 1.1

>> 1. the crop settings affect the current window mode, too 2.

>> implemented a similarity threshold setting, mainlly useful in games.

>> LION

>> always compares the current text with the one which has been spoken

>> previously. If it thinks the text hasn't changed, it doesn't speak.

>> This setting controls how aggressive LION is in comparing texts. 0

>> means all texts are identical, practically rendering the addon

>> unusable. 1 will read all texts, even if they are the same. The

>> default is 0.5.

>> version 1.0

>> initial version

>> Who wrote this, how often will I see updates?

>> My name is Stefan Moisei, a blind programmer trying to survive in an

>> East European country, Romania, who has a lot to catch up to get to

>> an occidental level. LION, and other blind specific software are just

>> a hobby for me, developed in my spare time. So, I'm afraid updates

>> won't come too often.

>> But

>> if you can code, this is NVDA, so the source is right there. :)

>> 

>> Sent from Mail for Windows 10

>> 

>> 

>> 

>> 

>> 

> --

> --

> --

> nothing is difficult unless you make it appear so.

> r. aravind,

> manager

> Department of sales

> bank of baroda specialised mortgage store, Chennai.

> mobile no: +91 9940369593,

> email id : aravind_069@..., aravind.andhrabank@....

> aravind.rajendran@....

>

 

 

--

Thanks/regards: Vaibhav Bhandari

 

 

 

 

 

 

 


Re: I greet thee with a bug report

Brandon Cole <Superblindman01@...>
 

Holy cow, this worked! The language was set to NE! Of all the silly little… Hahaha, thanks very much!

That said, I also want to report that I ran the SFC scan, and it actually did find and fix some corrupted files, so thanks for that. I will keep that one in my troubleshooting back pocket. I was just about to hop on and report that the SFC fix did not fix NVDA when I saw this new suggestion, tried it, and low and behold, it worked. Hahahahaha. Thanks again all!

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Thursday, August 20, 2020 7:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I greet thee with a bug report

 

Hi,

I think I know exactly what could have happened: if a system restart nor NVDA restart didn’t fix the problem and if this only affects NVDA interface, chances are that somehow NVDA’s interface language was set to a language you may not have heard of. To verify, either:

  1. Press Control+NVDA+R three times to see if NVDA starts speaking English. After that, restart NVDA, and configure NVDA to your liking again.
  2. With NVDA not running, open Run dialog (Windows+R) then type “%appdata%” without quotes, then open “nvda” folder. Locate a file named “nvda.ini” and look at what “language” line says. Change this line to “language = Windows”, making sure that tab character is preserved. Save the file and start NVDA.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, August 20, 2020 3:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I greet thee with a bug report

 

Were I you, I'd try uninstalling NVDA first.  Then following these instructions:

Using SFC (System File Checker) and DISM (Deployment Imaging Servicing and Management) to Repair Windows 8 & 10

Then restarting the machine again prior to doing a reinstall on NVDA.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

A gentleman is one who never hurts anyone's feelings unintentionally.

          ~ Oscar Wilde

 


Re: I greet thee with a bug report

 

On Thu, Aug 20, 2020 at 07:06 PM, Joseph Lee wrote:
that somehow NVDA’s interface language was set to a language you may not have heard of.
If this turns out to be the case, and it turns out that editing the nvda.ini file is necessary, I'd be very curious to know that the "language =" line read before being edited to "language = Windows".
 
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

A gentleman is one who never hurts anyone's feelings unintentionally.

          ~ Oscar Wilde

 


Re: I greet thee with a bug report

 

Hi,

I think I know exactly what could have happened: if a system restart nor NVDA restart didn’t fix the problem and if this only affects NVDA interface, chances are that somehow NVDA’s interface language was set to a language you may not have heard of. To verify, either:

  1. Press Control+NVDA+R three times to see if NVDA starts speaking English. After that, restart NVDA, and configure NVDA to your liking again.
  2. With NVDA not running, open Run dialog (Windows+R) then type “%appdata%” without quotes, then open “nvda” folder. Locate a file named “nvda.ini” and look at what “language” line says. Change this line to “language = Windows”, making sure that tab character is preserved. Save the file and start NVDA.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, August 20, 2020 3:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I greet thee with a bug report

 

Were I you, I'd try uninstalling NVDA first.  Then following these instructions:

Using SFC (System File Checker) and DISM (Deployment Imaging Servicing and Management) to Repair Windows 8 & 10

Then restarting the machine again prior to doing a reinstall on NVDA.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

A gentleman is one who never hurts anyone's feelings unintentionally.

          ~ Oscar Wilde

 


Re: I greet thee with a bug report

Brandon Cole <Superblindman01@...>
 

I am running windows 10, build 19041.450

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, August 20, 2020 7:00 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I greet thee with a bug report

 

In this case, even if SFC comes back clean when run initially, still follow it up with a run of DISM as well.

Also, what Windows are you running, version and build?
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

A gentleman is one who never hurts anyone's feelings unintentionally.

          ~ Oscar Wilde

 


Re: multiple instances of NVDA

Quentin Christensen
 

This is generally caused by something closing NVDA unexpectedly, such as it crashing, or if you go to task manager and "End task" it.  I haven't seen it when restarting or updating add-ons.  I wonder if it is a particular add-on which is not letting NVDA shut down cleanly?

If anyone replicates this, ideally with the log set to debug level, I'd be interested in your nvda-old.log file (the one from when NVDA didn't shut down properly).

If it's something in NVDA itself, then we definitely want to address it.  If it's something in an add-on then we can let the author know as well.

Quentin.

On Fri, Aug 21, 2020 at 8:47 AM Jim Pipczak <jim.pipczak@...> wrote:
Hi,

Try using tskill to remove NVDA out of memory to see if it works.

Press Windows r to get the run dialogue box and then type, tskill NVDA and press the enter key.

Thanks,
Jim


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Friday, 21 August 2020 7:22 AM
To: nvda@nvda.groups.io
Subject: [nvda] multiple instances of NVDA

It seems that if you close NVDA or restart it you will get multiple instances of NVDA in the system tray.  Right now I have four NVDA listings in my system tray.






Jim Pipczak
Access Technology Service Development Lead
Client Services
Vision Australia
14 & 17 Barrett Street Kensington VIC 3031

M: +614 3375 7598 T: +613 8378 1243 (I: 344243)
E: Jim.Pipczak@...
www.visionaustralia.org


Vision Australia is committed to supporting the blind and low vision community through COVID-19. Find out about our response and free support resources online at www.visionaustralia.org/COVID19.

[Vision Australia. Blindness. Low Vision.  Opportunity. - logo]

[Vision Australia. Winner of the Australian HR Award for Best Workplace Diversity and Inclusion Program. - logo]

Vision Australia acknowledges Aboriginal and Torres Strait Islander people as the traditional custodians of the land on which we operate. We have an inclusive culture and value diversity and all abilities.






--
Quentin Christensen
Training and Support Manager


Re: I greet thee with a bug report

 

In this case, even if SFC comes back clean when run initially, still follow it up with a run of DISM as well.

Also, what Windows are you running, version and build?
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

A gentleman is one who never hurts anyone's feelings unintentionally.

          ~ Oscar Wilde

 


Re: I greet thee with a bug report

Brandon Cole <Superblindman01@...>
 

OK, thanks. I’ll give that a shot as well.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, August 20, 2020 6:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I greet thee with a bug report

 

Were I you, I'd try uninstalling NVDA first.  Then following these instructions:

Using SFC (System File Checker) and DISM (Deployment Imaging Servicing and Management) to Repair Windows 8 & 10

Then restarting the machine again prior to doing a reinstall on NVDA.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

A gentleman is one who never hurts anyone's feelings unintentionally.

          ~ Oscar Wilde

 


Re: I greet thee with a bug report

 

Were I you, I'd try uninstalling NVDA first.  Then following these instructions:

Using SFC (System File Checker) and DISM (Deployment Imaging Servicing and Management) to Repair Windows 8 & 10

Then restarting the machine again prior to doing a reinstall on NVDA.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

A gentleman is one who never hurts anyone's feelings unintentionally.

          ~ Oscar Wilde

 


Re: I greet thee with a bug report

Brandon Cole <Superblindman01@...>
 

Thanks for this suggestion, but sadly it did not work. I ran the tool, restarted the whole system, and still have the same issue. Bah, I say. Bah.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Sent: Thursday, August 20, 2020 6:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I greet thee with a bug report

 

Hi

 

Try the following first it is found under the tools then the menu you want is called Run COM Registration Fixing tool...

Then follow the directions.

 

If you do not know how many times to get to those menus do the following if not spoken out.

 

nvda key + letter N to bring up the preferences menu then arrow down2 times this will put you on the tools menu there is a sub menuthen use the right arrow key to open the sub menu then arrow down 7 times this will put you on the com registration menu then press the enter key..

 

hopefully that fixes the problem for you. You might have to also reboot the pc for it to come right.

 

Gene nz

 

 

On 21/08/2020 9:46 am, Brandon Cole wrote:

Greetings,

I come seeking assistance with an NVDA bug that has recently sprung up. For some reason, NVDA will no longer read any of its own dialogs. The NVDA menu, the quit NVDA dialog, and so on. Furthermore, these dialogs no longer seem to have titles at all, let alone much content in them. Running NVDA whilst also running Jaws just to be sure showed me this. When bringing up the NVDA menu, NVDA said nothing at all, but even Jaws only said “submenu, submenu, submenu” as I browsed through the items. What’s more, anything that had an associated hot key didn’t seem to have one. Instead of saying Alt Plus T or Alt Plus B for example, what I heard was “Alt Plus…” And then simply nothing. I even uninstalled NVDA and reinstalled it, only to discover the issue persisted even during the reinstallation. It is a very disconcerting bug, and I am desperately hoping someone else has heard of this before. Thanks for any help you can provide. One final note for whatever it’s worth, this bug only seems to affect NVDA. Jaws is just fine.

Thanks all!

 

 


Re: multiple instances of NVDA

Jim Pipczak
 

Hi,

Try using tskill to remove NVDA out of memory to see if it works.

Press Windows r to get the run dialogue box and then type, tskill NVDA and press the enter key.

Thanks,
Jim

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Friday, 21 August 2020 7:22 AM
To: nvda@nvda.groups.io
Subject: [nvda] multiple instances of NVDA

It seems that if you close NVDA or restart it you will get multiple instances of NVDA in the system tray. Right now I have four NVDA listings in my system tray.






Jim Pipczak
Access Technology Service Development Lead
Client Services
Vision Australia
14 & 17 Barrett Street Kensington VIC 3031

M: +614 3375 7598 T: +613 8378 1243 (I: 344243)
E: Jim.Pipczak@visionaustralia.org
www.visionaustralia.org


Vision Australia is committed to supporting the blind and low vision community through COVID-19. Find out about our response and free support resources online at www.visionaustralia.org/COVID19.

[Vision Australia. Blindness. Low Vision. Opportunity. - logo]

[Vision Australia. Winner of the Australian HR Award for Best Workplace Diversity and Inclusion Program. - logo]

Vision Australia acknowledges Aboriginal and Torres Strait Islander people as the traditional custodians of the land on which we operate. We have an inclusive culture and value diversity and all abilities.


Re: in this group is my 1st mail

Quentin Christensen
 

We're here :)

Welcome, and do please let us know if there's anything we can help with.

Quentin.

On Fri, Aug 21, 2020 at 3:10 AM ( NAJAF . Naqvi ) <najafnaqvi471@...> wrote:
I want nvaccess to help you

On Thu, Aug 20, 2020 at 10:04 PM Jesse Farquharson <jesse100rules@...> wrote:

Hey there,

How can we help you?



--
Quentin Christensen
Training and Support Manager


Re: I greet thee with a bug report

 

Hi.

Yeah, I get this sometimes usually on system startup.

nvda control n will not work, menu up but not read hit it again, menu will go away but no read.

Fix, wait for a bit and it will fix itself or click nvda icon in the tray then it read then the keys work again.

Crash on brousers and half of it freezes.

If you restart nvda it will be fine, it will log a freeze though.

notification tree going unknown.

Restart windows.

Usually its a crash where another program has exited then crashed and not exited properly.

Not sure how to get all this to work right but nvda has been at least a lot better with the last 2.

But put the system under stress and yeah it can happen.

Remember that when nvda starts, don't immediately do something especially after a windows startup as the system may not be fully booted.

Even with my flash ssd systems I have not everything is running and some stuff may take time to pop up.



On 21/08/2020 9:46 am, Brandon Cole wrote:

Greetings,

I come seeking assistance with an NVDA bug that has recently sprung up. For some reason, NVDA will no longer read any of its own dialogs. The NVDA menu, the quit NVDA dialog, and so on. Furthermore, these dialogs no longer seem to have titles at all, let alone much content in them. Running NVDA whilst also running Jaws just to be sure showed me this. When bringing up the NVDA menu, NVDA said nothing at all, but even Jaws only said “submenu, submenu, submenu” as I browsed through the items. What’s more, anything that had an associated hot key didn’t seem to have one. Instead of saying Alt Plus T or Alt Plus B for example, what I heard was “Alt Plus…” And then simply nothing. I even uninstalled NVDA and reinstalled it, only to discover the issue persisted even during the reinstallation. It is a very disconcerting bug, and I am desperately hoping someone else has heard of this before. Thanks for any help you can provide. One final note for whatever it’s worth, this bug only seems to affect NVDA. Jaws is just fine.

Thanks all!

 

 


Re: I greet thee with a bug report

hurrikennyandopo ...
 

Hi


Try the following first it is found under the tools then the menu you want is called Run COM Registration Fixing tool...

Then follow the directions.


If you do not know how many times to get to those menus do the following if not spoken out.


nvda key + letter N to bring up the preferences menu then arrow down2 times this will put you on the tools menu there is a sub menuthen use the right arrow key to open the sub menu then arrow down 7 times this will put you on the com registration menu then press the enter key..


hopefully that fixes the problem for you. You might have to also reboot the pc for it to come right.


Gene nz

 


On 21/08/2020 9:46 am, Brandon Cole wrote:

Greetings,

I come seeking assistance with an NVDA bug that has recently sprung up. For some reason, NVDA will no longer read any of its own dialogs. The NVDA menu, the quit NVDA dialog, and so on. Furthermore, these dialogs no longer seem to have titles at all, let alone much content in them. Running NVDA whilst also running Jaws just to be sure showed me this. When bringing up the NVDA menu, NVDA said nothing at all, but even Jaws only said “submenu, submenu, submenu” as I browsed through the items. What’s more, anything that had an associated hot key didn’t seem to have one. Instead of saying Alt Plus T or Alt Plus B for example, what I heard was “Alt Plus…” And then simply nothing. I even uninstalled NVDA and reinstalled it, only to discover the issue persisted even during the reinstallation. It is a very disconcerting bug, and I am desperately hoping someone else has heard of this before. Thanks for any help you can provide. One final note for whatever it’s worth, this bug only seems to affect NVDA. Jaws is just fine.

Thanks all!

 

 


Re: multiple instances of NVDA

 

I get this behavior not infrequently.  They usually clean themselves up over time, but if you try to activate any of the ones that are "ghost icons" they disappear and do nothing.  There's only ever been one actual running instance of NVDA.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

A gentleman is one who never hurts anyone's feelings unintentionally.

          ~ Oscar Wilde

 


I greet thee with a bug report

Brandon Cole <Superblindman01@...>
 

Greetings,

I come seeking assistance with an NVDA bug that has recently sprung up. For some reason, NVDA will no longer read any of its own dialogs. The NVDA menu, the quit NVDA dialog, and so on. Furthermore, these dialogs no longer seem to have titles at all, let alone much content in them. Running NVDA whilst also running Jaws just to be sure showed me this. When bringing up the NVDA menu, NVDA said nothing at all, but even Jaws only said “submenu, submenu, submenu” as I browsed through the items. What’s more, anything that had an associated hot key didn’t seem to have one. Instead of saying Alt Plus T or Alt Plus B for example, what I heard was “Alt Plus…” And then simply nothing. I even uninstalled NVDA and reinstalled it, only to discover the issue persisted even during the reinstallation. It is a very disconcerting bug, and I am desperately hoping someone else has heard of this before. Thanks for any help you can provide. One final note for whatever it’s worth, this bug only seems to affect NVDA. Jaws is just fine.

Thanks all!

 

 


Re: multiple instances of NVDA

 

These will happen on nvda exit and restart.

on nvda crash.

on nvda addon update.

These are not a general issue usually unless you need to heavily rely on the tray.

I don't usually need the tray or the shell or anything for normal computer tasks in fact for where I need I have found ways around various system issues I have had.



On 21/08/2020 10:08 am, Sarah k Alawami wrote:

I've ben able to reproduce this off and on, more off than on on both my base pc running windows 2004 and my shadow running 1909. They do clear themselves up sometimes though.

--

Sarah Alawami, owner of TFFP. . For more info go to our website.

Check out my adventures with a shadow machine.

to subscribe to the feed click here and you can also follow us on twitter

Our discord is where you will know when we go live on twitch. Feel free to give the channel a follow and see what is up there.

For stream archives, products you can buy and more visit my main lbry page and my tffp lbry page You will also be able to buy some of my products and eBooks there.

Finally, to become a patron and help support the podcast go here

On 20 Aug 2020, at 14:21, Don H wrote:

It seems that if you close NVDA or restart it you will get multiple instances of NVDA in the system tray.  Right now I have four NVDA listings in my system tray.

11261 - 11280 of 87660