1. nvda@nvda.groups.io
   Date   
Re: When Nvda keys appear to freeze, also window keys appear to freeze.

Hareth
 

Even without addons that happens here.
I deal with it as a minor thing, goes away with restarting NVDA.
BTW its not just a new NVDA version issue, Its was occurring for years
here now specially since win10 came up NVDA key would stop functioning
every now and then. I thought it was happening because I change usage
between FS JAWS and NVDA so often in one session.
I might been wrong though.

On 7/27/20, Quentin Christensen <quentin@nvaccess.org> wrote:
Sarah,

You have a bunch of add-ons running there, if you restart NVDA without them
does it make a difference?

On Sun, Jul 26, 2020 at 5:10 AM Sarah k Alawami <marrie12@gmail.com> wrote:

Using Nvda version 20. On windows 10 1909. I noticed that the keys will
freeze. That is, control left in control right, and things like that. I
know that someone reported this before. We starting Nvda works to fix
this.
I’ve also done the Com registration tool as well. I’ve seen us in
Thunderbird, discord, jarred, just about everywhere. Here’s a log.


https://www.dropbox.com/s/fzi3e5ha0qturc4/nvda%20log%20when%20keys%20frees%20.log?dl=1

Get Outlook for iOS <https://aka.ms/o0ukef>;


--
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>;
Re: Digest Speaks In Foreign Language With NVDA

Tyler Spivey
 

Probably automatic language switching. Turn it off in NVDA, Preferences,
Settings, Speech.

On 7/26/2020 9:46 PM, Glenn / Lenny wrote:
 
Hi,
If I open the NVDA digest with NVDA, it all sounds foreign, like maybe
German.
NVDA only does this in the digest for this list.
Jaws does not do this.
What would have caused this for my NVDA?
Like I mentioned, I only notice it in this digest message, and all the
NVDA digest messages, and not with Jaws.
Glenn
Digest Speaks In Foreign Language With NVDA

Glenn / Lenny
 

 
Hi,
If I open the NVDA digest with NVDA, it all sounds foreign, like maybe German.
NVDA only does this in the digest for this list.
Jaws does not do this.
What would have caused this for my NVDA?
Like I mentioned, I only notice it in this digest message, and all the NVDA digest messages, and not with Jaws.
Glenn
Re: unknown still here

Robert Doc Wright godfearer
 

unfortunately, even after rebooting the problem is still there. I'll just
wait.

----- Original Message -----
From: "Tyler Spivey" <tspivey@pcdesk.net>
To: <nvda@nvda.groups.io>
Sent: Saturday, July 25, 2020 9:40 PM
Subject: Re: [nvda] unknown still here


This should solve your problem.

https://nvda.groups.io/g/nvda/message/71405



On 7/25/2020 7:57 PM, Robert Doc Wright godfearer wrote:
I ran the fixing tool but the problem still exists.
Below is the log:
____________
INFO - __main__ (20:24:26.271) - MainThread (21644):
Starting NVDA version 2020.1
INFO - core.main (20:24:26.864) - MainThread (21644):
Config dir: C:\Users\wrigh\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (20:24:26.864) - MainThread
(21644):
Loading config: C:\Users\wrigh\AppData\Roaming\nvda\nvda.ini
INFO - core.main (20:24:26.917) - MainThread (21644):
Using Windows version 10.0.18363 workstation
INFO - core.main (20:24:26.917) - MainThread (21644):
Using Python version 3.7.7 (tags/v3.7.7:d7c567b08f, Mar 10 2020,
09:44:33) [MSC v.1900 32 bit (Intel)]
INFO - core.main (20:24:26.917) - MainThread (21644):
Using comtypes version 1.1.7
INFO - core.main (20:24:26.917) - MainThread (21644):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (20:24:27.272) - MainThread (21644):
Loaded synthDriver oneCore
INFO - core.main (20:24:27.272) - MainThread (21644):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version
1.12.0
INFO - brailleInput.initialize (20:24:27.286) - MainThread (21644):
Braille input initialized
INFO - braille.initialize (20:24:27.286) - MainThread (21644):
Using liblouis version 3.12.0
INFO - braille.initialize (20:24:27.289) - MainThread (21644):
Using pySerial version 3.4
INFO - braille.BrailleHandler.setDisplayByName (20:24:27.292) -
MainThread (21644):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - core.main (20:24:27.396) - MainThread (21644):
Java Access Bridge support initialized
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (20:24:27.405) -
_UIAHandler.UIAHandler.MTAThread (21480):
UIAutomation: IUIAutomation6
INFO - core.main (20:24:27.585) - MainThread (21644):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (20:24:27.600) -
MainThread (21644):
Performing automatic update check
________


******Very funny Scotty ... now beam down my clothes !

Family times where there is fun for every ear!
http://stream.wrighthere.net:8000/stream.mp3
Re: unknown still here

Robert Doc Wright godfearer
 

What is strange is that I am not having this problem on my laptop. Just when
I got my new desktop.

----- Original Message -----
From: "Tyler Spivey" <tspivey@pcdesk.net>
To: <nvda@nvda.groups.io>
Sent: Saturday, July 25, 2020 9:40 PM
Subject: Re: [nvda] unknown still here


This should solve your problem.

https://nvda.groups.io/g/nvda/message/71405



On 7/25/2020 7:57 PM, Robert Doc Wright godfearer wrote:
I ran the fixing tool but the problem still exists.
Below is the log:
____________
INFO - __main__ (20:24:26.271) - MainThread (21644):
Starting NVDA version 2020.1
INFO - core.main (20:24:26.864) - MainThread (21644):
Config dir: C:\Users\wrigh\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (20:24:26.864) - MainThread
(21644):
Loading config: C:\Users\wrigh\AppData\Roaming\nvda\nvda.ini
INFO - core.main (20:24:26.917) - MainThread (21644):
Using Windows version 10.0.18363 workstation
INFO - core.main (20:24:26.917) - MainThread (21644):
Using Python version 3.7.7 (tags/v3.7.7:d7c567b08f, Mar 10 2020,
09:44:33) [MSC v.1900 32 bit (Intel)]
INFO - core.main (20:24:26.917) - MainThread (21644):
Using comtypes version 1.1.7
INFO - core.main (20:24:26.917) - MainThread (21644):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (20:24:27.272) - MainThread (21644):
Loaded synthDriver oneCore
INFO - core.main (20:24:27.272) - MainThread (21644):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version
1.12.0
INFO - brailleInput.initialize (20:24:27.286) - MainThread (21644):
Braille input initialized
INFO - braille.initialize (20:24:27.286) - MainThread (21644):
Using liblouis version 3.12.0
INFO - braille.initialize (20:24:27.289) - MainThread (21644):
Using pySerial version 3.4
INFO - braille.BrailleHandler.setDisplayByName (20:24:27.292) -
MainThread (21644):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - core.main (20:24:27.396) - MainThread (21644):
Java Access Bridge support initialized
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (20:24:27.405) -
_UIAHandler.UIAHandler.MTAThread (21480):
UIAutomation: IUIAutomation6
INFO - core.main (20:24:27.585) - MainThread (21644):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (20:24:27.600) -
MainThread (21644):
Performing automatic update check
________


******Very funny Scotty ... now beam down my clothes !

Family times where there is fun for every ear!
http://stream.wrighthere.net:8000/stream.mp3
Re: problems with hot keys

Quentin Christensen
 

Odd,

If someone can capture a log at debug level that would be really helpful please!

Quentin.

On Mon, Jul 27, 2020 at 1:40 PM Luke Davis <luke@...> wrote:
Yes. This happened from time to time with older versions, but I've been seeing
it a lot more with recent versions (beta, RC, and alpha).

I haven't been able to figure out if it is NVDA's fault, or some change in
Windows 2004.

I have yet to capture a log on it, as it usually happens when I'm in a hurry.

I believe it used to happen more with Firefox, whereas now it seems to happen
for just about any application.  Also it no longer seems to happen only after a
machine suspend.

Not only is the NVDA key no longer functional in these cases (I.E. NVDA+Q does
nothing but type a Q), even more perplexing to me is that Ctrl+Alt+N fails to
launch the desktop shortcut.
Which implies something about the keyboard driver I think, although Restarting
NVDA from the systray icon still fixes the problem.

Luke

On Sat, 25 Jul 2020, Don H wrote:

> I am running the latest released version of NVDA on a Win10 2004 laptop.  On
> a random basis I am running into the problem where all the hotkeys for Nvda
> stop working.    Is anyone else seeing this problem?  Can't even close VNDA
> as the insert q doesn't work





--
Quentin Christensen
Training and Support Manager
Re: problems with hot keys

Luke Davis
 

Yes. This happened from time to time with older versions, but I've been seeing it a lot more with recent versions (beta, RC, and alpha).

I haven't been able to figure out if it is NVDA's fault, or some change in Windows 2004.

I have yet to capture a log on it, as it usually happens when I'm in a hurry.

I believe it used to happen more with Firefox, whereas now it seems to happen for just about any application. Also it no longer seems to happen only after a machine suspend.

Not only is the NVDA key no longer functional in these cases (I.E. NVDA+Q does nothing but type a Q), even more perplexing to me is that Ctrl+Alt+N fails to launch the desktop shortcut.
Which implies something about the keyboard driver I think, although Restarting NVDA from the systray icon still fixes the problem.

Luke

On Sat, 25 Jul 2020, Don H wrote:

I am running the latest released version of NVDA on a Win10 2004 laptop.  On a random basis I am running into the problem where all the hotkeys for Nvda stop working.    Is anyone else seeing this problem?  Can't even close VNDA as the insert q doesn't work
Re: When Nvda keys appear to freeze, also window keys appear to freeze.

Sarah k Alawami
 

I don't think it will. I've had it freeze with add ons disabled and sometimes when it happens I'm in TBird and it freezes. I'm not connected to that machine right now or I would test. It actually has happened with my base machine as well. When I restart nvda it works until it decided to brake again. I know this was reported months ago, not by me but I seem to remember someone else having this issue, maybe?

--

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 26 Jul 2020, at 16:29, Quentin Christensen wrote:

Sarah,

You have a bunch of add-ons running there, if you restart NVDA without them does it make a difference?

On Sun, Jul 26, 2020 at 5:10 AM Sarah k Alawami <marrie12@...> wrote:
Using Nvda version 20. On windows 10 1909. I noticed that the keys will freeze. That is, control left in control right, and things like that. I know that someone reported this before. We starting Nvda works to fix this. I’ve also done the Com registration tool as well. I’ve seen us in Thunderbird, discord, jarred, just about everywhere. Here’s a log.




--
Quentin Christensen
Training and Support Manager
Re: problems with hot keys

Gene
 

When you move using the arrow keys in a list like the desktop. does NVDA read? In other words, is it just short cut commands regardding NVDA that don't work? Moving through the desktop and having things read is a Windows command. Likewise, moving through a document with down arrow, for example, and having NVDA read is a program command that works in any edit field.

Gene

-----Original Message-----
From: Betsy Grenevitch
Sent: Sunday, July 26, 2020 7:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] problems with hot keys



I have no idea. When I do NVDA-F2 it says


"pass next key group". With number lock off On 7/26/2020 7:25 PM, Quentin Christensen wrote:and I push the 8 key it does not say anything. Thanks for trying to help me, though.


At that point, is NVDA still reading information? What keyboard / keyboard driver are you using? I think I recall something with a particular one, but I can't find it now.

If you press NVDA+Q and restart with add-ons disabled, does it make a difference? If not, if you could send me a copy of your NVDA log, at debug level, I can have a look:

First of all, your NVDA key is either INSERT or CAPS LOCK, depending on how you have NVDA setup. So, to set your log level:
1) Press NVDA+control+g to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+control+c to save settings.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, recreate the issue - do whatever causes problems.

To get NVDA's log after that, there are several ways:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Open your email and start a message to info@nvaccess.org, type a little about what you have done and what has happened in the body of the message, then leave a space and:
5) Press CONTROL+V to paste the copied log.

Instead of using the log viewer, or if NVDA has stopped and you needed to restart it or the computer:
1) Press WINDOWS+R to open Windows' Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letter t e m p and another percent sign). Windows Explorer should open to the temporary folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files: nvda.log (the log file for the current or most recent NVDA session), nvda-old.og (the log from the previous session) and nvda-crash.dmp (a crash dump with more information created if NVDA itself crashes).
5) Depending on what email program you use, the steps will be different, but attach as many of those three files to an email to info@nvaccess.org as will be useful, and again in the body of the message describe a bit about what has happened.


On Sun, Jul 26, 2020 at 4:32 AM Don H <lmddh50@adams.net> wrote:
I am running the latest released version of NVDA on a Win10 2004
laptop. On a random basis I am running into the problem where all the
hotkeys for Nvda stop working. Is anyone else seeing this problem?
Can't even close VNDA as the insert q doesn't work









--

Quentin Christensen
Training and Support Manager


Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
-- Betsy Grenevitch 678-862-3876
Re: problems with hot keys

Betsy Grenevitch
 

Sorry, I responded to the incorrect email.

On 7/26/2020 7:25 PM, Quentin Christensen wrote:
At that point, is NVDA still reading information?  What keyboard / keyboard driver are you using?  I think I recall something with a particular one, but I can't find it now.

If you press NVDA+Q and restart with add-ons disabled, does it make a difference?  If not, if you could send me a copy of your NVDA log, at debug level, I can have a look:

First of all, your NVDA key is either INSERT or CAPS LOCK, depending on how you have NVDA setup.  So, to set your log level:
1) Press NVDA+control+g to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+control+c to save settings.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, recreate the issue - do whatever causes problems.

To get NVDA's log after that, there are several ways:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Open your email and start a message to info@..., type a little about what you have done and what has happened in the body of the message, then leave a space and:
5) Press CONTROL+V to paste the copied log.

Instead of using the log viewer, or if NVDA has stopped and you needed to restart it or the computer:
1) Press WINDOWS+R to open Windows' Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letter t e m p and another percent sign).  Windows Explorer should open to the temporary folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log file for the current or most recent NVDA session), nvda-old.og (the log from the previous session) and nvda-crash.dmp (a crash dump with more information created if NVDA itself crashes).
5) Depending on what email program you use, the steps will be different, but attach as many of those three files to an email to info@... as will be useful, and again in the body of the message describe a bit about what has happened.

On Sun, Jul 26, 2020 at 4:32 AM Don H <lmddh50@...> wrote:
I am running the latest released version of NVDA on a Win10 2004
laptop.  On a random basis I am running into the problem where all the
hotkeys for Nvda stop working.    Is anyone else seeing this problem? 
Can't even close VNDA as the insert q doesn't work







--
Quentin Christensen
Training and Support Manager

-- 
Betsy Grenevitch
678-862-3876
Re: problems with hot keys

Betsy Grenevitch
 

I have no idea. When I do NVDA-F2 it says

 "pass next key group". With number lock off On 7/26/2020 7:25 PM, Quentin Christensen wrote:and I push the 8 key it does not say anything. Thanks for trying to help me, though.

At that point, is NVDA still reading information?  What keyboard / keyboard driver are you using?  I think I recall something with a particular one, but I can't find it now.

If you press NVDA+Q and restart with add-ons disabled, does it make a difference?  If not, if you could send me a copy of your NVDA log, at debug level, I can have a look:

First of all, your NVDA key is either INSERT or CAPS LOCK, depending on how you have NVDA setup.  So, to set your log level:
1) Press NVDA+control+g to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+control+c to save settings.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, recreate the issue - do whatever causes problems.

To get NVDA's log after that, there are several ways:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Open your email and start a message to info@..., type a little about what you have done and what has happened in the body of the message, then leave a space and:
5) Press CONTROL+V to paste the copied log.

Instead of using the log viewer, or if NVDA has stopped and you needed to restart it or the computer:
1) Press WINDOWS+R to open Windows' Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letter t e m p and another percent sign).  Windows Explorer should open to the temporary folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log file for the current or most recent NVDA session), nvda-old.og (the log from the previous session) and nvda-crash.dmp (a crash dump with more information created if NVDA itself crashes).
5) Depending on what email program you use, the steps will be different, but attach as many of those three files to an email to info@... as will be useful, and again in the body of the message describe a bit about what has happened.

On Sun, Jul 26, 2020 at 4:32 AM Don H <lmddh50@...> wrote:
I am running the latest released version of NVDA on a Win10 2004
laptop.  On a random basis I am running into the problem where all the
hotkeys for Nvda stop working.    Is anyone else seeing this problem? 
Can't even close VNDA as the insert q doesn't work







--
Quentin Christensen
Training and Support Manager

-- 
Betsy Grenevitch
678-862-3876
Re: When Nvda keys appear to freeze, also window keys appear to freeze.

Quentin Christensen
 

Sarah,

You have a bunch of add-ons running there, if you restart NVDA without them does it make a difference?

On Sun, Jul 26, 2020 at 5:10 AM Sarah k Alawami <marrie12@...> wrote:
Using Nvda version 20. On windows 10 1909. I noticed that the keys will freeze. That is, control left in control right, and things like that. I know that someone reported this before. We starting Nvda works to fix this. I’ve also done the Com registration tool as well. I’ve seen us in Thunderbird, discord, jarred, just about everywhere. Here’s a log.




--
Quentin Christensen
Training and Support Manager
Re: problems with hot keys

Quentin Christensen
 

At that point, is NVDA still reading information?  What keyboard / keyboard driver are you using?  I think I recall something with a particular one, but I can't find it now.

If you press NVDA+Q and restart with add-ons disabled, does it make a difference?  If not, if you could send me a copy of your NVDA log, at debug level, I can have a look:

First of all, your NVDA key is either INSERT or CAPS LOCK, depending on how you have NVDA setup.  So, to set your log level:
1) Press NVDA+control+g to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+control+c to save settings.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, recreate the issue - do whatever causes problems.

To get NVDA's log after that, there are several ways:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Open your email and start a message to info@..., type a little about what you have done and what has happened in the body of the message, then leave a space and:
5) Press CONTROL+V to paste the copied log.

Instead of using the log viewer, or if NVDA has stopped and you needed to restart it or the computer:
1) Press WINDOWS+R to open Windows' Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letter t e m p and another percent sign).  Windows Explorer should open to the temporary folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log file for the current or most recent NVDA session), nvda-old.og (the log from the previous session) and nvda-crash.dmp (a crash dump with more information created if NVDA itself crashes).
5) Depending on what email program you use, the steps will be different, but attach as many of those three files to an email to info@... as will be useful, and again in the body of the message describe a bit about what has happened.


On Sun, Jul 26, 2020 at 4:32 AM Don H <lmddh50@...> wrote:
I am running the latest released version of NVDA on a Win10 2004
laptop.  On a random basis I am running into the problem where all the
hotkeys for Nvda stop working.    Is anyone else seeing this problem? 
Can't even close VNDA as the insert q doesn't work







--
Quentin Christensen
Training and Support Manager
Any hint to read YouTube (and perhaps other) subtitles?

Alexandre Alves Toco
 

Hi friends.

I noticed that, if I check the option to include automatically generated subtitles, nvda will read the subtitles of the vídeo.

How ever, it reads the same thing over and over again.

Suppose that the vídeo has the sentence: last year I was visiting france.

Nvda is Reading as follows:

Last

Last year

Last year I

Last year I was

 

Is there any hint to make nvda to read the complete sentence only once?

 

 

 

Enviado do Email para Windows 10

 
Re: Musescore and his accessibility with NVDA

Jaffar Sidek
 

Hi.  Musescore since version 2 has been accessible with NVDA. They have a set of jaws scripts too to make it more accessible with Jaws.  Cheers!

On 27/7/2020 4:33 am, Marco Oros wrote:
Hello.

I have a question.

Which version of Musescore is accessible for NVDA users?

Thank You.

Marco
Musescore and his accessibility with NVDA

Marco Oros
 

Hello.

I have a question.

Which version of Musescore is accessible for NVDA users?

Thank You.

Marco
for those Spanish speakers "ActualidadAccesible? brings you the 2nd part of NVDA series Addons

Gerardo Corripio
 

NVDA: nociones básicas complementos parte 2 2020 https://actualidadaccesible.com/2020/07/26/nvda-nociones-basicas-complementos/


Gera
Enviado desde mi iPhone SE (2nd Generation) de Telcel
accessing the settings of the handytech braille display while using NVDA

Cristina Ebetiuc
 

Hi

Is there a Hotkey to accessing the Settings of the Handytech active star Braille Display while using NVDA?

thanks

 

Gesendet von Mail für Windows 10

 
locked Re: Contact

Brian Vogel
 

Ibrahim,

         This question would be appropriate for the Chat Subgroup, but definitely not here, and I wouldn't recommend the Chat Subgroup, either.

          Both the Android Accessibility and PhonesForTheBlind groups on Groups.io would be far better places to ask this question.

          As this is entirely off-topic here, and there are venues where it's dead on-topic and would get the attention it needs, this topic is now locked.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 
Re: unknown still here

Tyler Spivey
 

This should solve your problem.

https://nvda.groups.io/g/nvda/message/71405

On 7/25/2020 7:57 PM, Robert Doc Wright godfearer wrote:
I ran the fixing tool but the problem still exists.
Below is the log:
____________
INFO - __main__ (20:24:26.271) - MainThread (21644):
Starting NVDA version 2020.1
INFO - core.main (20:24:26.864) - MainThread (21644):
Config dir: C:\Users\wrigh\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (20:24:26.864) - MainThread (21644):
Loading config: C:\Users\wrigh\AppData\Roaming\nvda\nvda.ini
INFO - core.main (20:24:26.917) - MainThread (21644):
Using Windows version 10.0.18363 workstation
INFO - core.main (20:24:26.917) - MainThread (21644):
Using Python version 3.7.7 (tags/v3.7.7:d7c567b08f, Mar 10 2020,
09:44:33) [MSC v.1900 32 bit (Intel)]
INFO - core.main (20:24:26.917) - MainThread (21644):
Using comtypes version 1.1.7
INFO - core.main (20:24:26.917) - MainThread (21644):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (20:24:27.272) - MainThread (21644):
Loaded synthDriver oneCore
INFO - core.main (20:24:27.272) - MainThread (21644):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0
INFO - brailleInput.initialize (20:24:27.286) - MainThread (21644):
Braille input initialized
INFO - braille.initialize (20:24:27.286) - MainThread (21644):
Using liblouis version 3.12.0
INFO - braille.initialize (20:24:27.289) - MainThread (21644):
Using pySerial version 3.4
INFO - braille.BrailleHandler.setDisplayByName (20:24:27.292) -
MainThread (21644):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - core.main (20:24:27.396) - MainThread (21644):
Java Access Bridge support initialized
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (20:24:27.405) -
_UIAHandler.UIAHandler.MTAThread (21480):
UIAutomation: IUIAutomation6
INFO - core.main (20:24:27.585) - MainThread (21644):
NVDA initialized
INFO - updateCheck.AutoUpdateChecker._started (20:24:27.600) -
MainThread (21644):
Performing automatic update check
________
 
 
******Very funny Scotty ... now beam down my clothes !
 
Family times where there is fun for every ear!
http://stream.wrighthere.net:8000/stream.mp3
5361 - 5380 of 81015  
More
Home Messages Hashtags Subgroups About Features Pricing Updates Terms Help Twitter