NVDA Stopped Reading Putty


Gary
 

I am using the latest release of NVDA (2020.4) on Windows 10. My job
requires that I work on Linux systems ll day, which I do via Putty.
This afternoon, out of nowhere, NVDA stopped automatically reading the
output of the Putty windows, making my job impossible. I'm dead in
the water, basically.

Does anybody have any ideas what would cause this? I don't see any
settings that control this. I'm out of ideas and frazzled.

Gary


benmoxey@...
 

Hi Gary

I'm guessing the reporting of dynamic content changes has been accidently turned off.

Toggle this feature with NVDA + 5 (on the number row).

You can find this option in the Object Presentation Settings screen with Control + NVDA + O.

Cheers

Ben

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Wednesday, 5 May 2021 5:35 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Stopped Reading Putty

I am using the latest release of NVDA (2020.4) on Windows 10. My job requires that I work on Linux systems ll day, which I do via Putty.
This afternoon, out of nowhere, NVDA stopped automatically reading the output of the Putty windows, making my job impossible. I'm dead in the water, basically.

Does anybody have any ideas what would cause this? I don't see any settings that control this. I'm out of ideas and frazzled.

Gary


Gary
 

That was it.  Thank you so much!


On Tue, May 4, 2021 at 04:07 PM, <benmoxey@...> wrote:
Hi Gary

I'm guessing the reporting of dynamic content changes has been accidently turned off.

Toggle this feature with NVDA + 5 (on the number row).

You can find this option in the Object Presentation Settings screen with Control + NVDA + O.

Cheers

Ben



Chris Smart
 

What happens if you toggle NVDA+5, reporting of dynamic content changes?


 Accidentally turned this off and it broke some things here.

\


On 2021-05-04 3:34 p.m., Gary wrote:

I am using the latest release of NVDA (2020.4) on Windows 10.  My job
requires that I work on Linux systems ll day, which I do via Putty.
This afternoon, out of nowhere, NVDA stopped automatically reading the
output of the Putty windows, making my job impossible.  I'm dead in
the water, basically.

Does anybody have any ideas what would cause this?  I don't see any
settings that control this.  I'm out of ideas and frazzled.

Gary






Chris Smart
 

Whoops someone beat me to it. :)



On 2021-05-04 4:15 p.m., Gary wrote:

That was it.  Thank you so much!


On Tue, May 4, 2021 at 04:07 PM, <benmoxey@...> wrote:
Hi Gary

I'm guessing the reporting of dynamic content changes has been accidently turned off.

Toggle this feature with NVDA + 5 (on the number row).

You can find this option in the Object Presentation Settings screen with Control + NVDA + O.

Cheers

Ben



Luke Davis
 

No idea in particular, but you might try the windows native ssh client. It may work better for some reason.
Or open a bash shell under WSL, and use SSH from there.

As for NVDA: try starting it with add-ons disabled. It may be that there was an add-on update, and it had a negative effect.

I don't know if the COM Registration Fixing Tool can help you here, but it won't hurt to try it (NVDA tools menu).

Also, normal Windows trouble shooting steps of
SFC /ScanNow
and:
DISM /Online /Cleanup-Image /RestoreHealth

Might help, depending on what's actually wrong.

Luke
May the fourth be with you all.

Gary wrote:

I am using the latest release of NVDA (2020.4) on Windows 10. My job
requires that I work on Linux systems ll day, which I do via Putty.
This afternoon, out of nowhere, NVDA stopped automatically reading the
output of the Putty windows, making my job impossible. I'm dead in
the water, basically.


Thomas N. Chan
 

For my experience with shell client like putty, I usually create session log which I can review on the go or later.
Sometimes, the session or information are way too long or too much that any screen reader cannot pick up or overlook.
 
Thats what I will do to cover my reviewing part just in case I didn't hear it or screen reader miss it.

 
Regards,
Thomas N. Chan