Running NVDA 2017-3 on a Win 10 64 bit Fall Creator edition laptop. On what seems to be a random thing on numerous occasions when I hit the windows key to open up the start menu NVDA simply goes away. I have no speech and hitting insert n to open the NVDA UI does nothing. Is there a way to capture what is happening to NVDA? Under the nvda tools menu view log only shows what I think is the restrt of NVDA when I start NVDA again with control alt n. Thanks
|
|
I encounter the same issue sometimes. After 2 or 3 Minutes the speech works again. I just wait for that since it does not happen every time when I hit the Windows key. It specially ocures when a browser is running at the same time. It is quite annoying in some situations.
Best Adriani
Von meinem iPhone gesendet
toggle quoted messageShow quoted text
Am 06.11.2017 um 23:49 schrieb Don H <lmddh50@...>:
Running NVDA 2017-3 on a Win 10 64 bit Fall Creator edition laptop. On what seems to be a random thing on numerous occasions when I hit the windows key to open up the start menu NVDA simply goes away. I have no speech and hitting insert n to open the NVDA UI does nothing. Is there a way to capture what is happening to NVDA? Under the nvda tools menu view log only shows what I think is the restrt of NVDA when I start NVDA again with control alt n. Thanks
|
|
We don't know if NVDA is crashing. Just
because speech stops doesn't mean the screen-reader is crashing. The
speech synthesizer could be crashing as well. Would such an event be in
the log? What synthesizer is being used?
Â
Gene
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Monday, November 06, 2017 5:06 PM
Subject: Re: [nvda] NVDA crashing
I encounter the same issue sometimes. After 2 or 3 Minutes the
speech works again. I just wait for that since it does not happen every time
when I hit the Windows key. It specially ocures when a browser is running at the
same time. It is quite annoying in some
situations. Best Adriani Von meinem iPhone
gesendet > Am 06.11.2017 um 23:49 schrieb Don H < lmddh50@...>: > >
Running NVDA 2017-3 on a Win 10 64 bit Fall Creator edition laptop. > On
what seems to be a random thing on numerous occasions when I hit the windows key
to open up the start menu NVDA simply goes away. I have no speech and
hitting insert n to open the NVDA UI does nothing. Is there a way to
capture what is happening to NVDA? Under the nvda tools menu view log only
shows what I think is the restrt of NVDA when I start NVDA again with control
alt n. > Thanks > > > >
|
|
Brian's Mail list account
When you restart nvda. go to run and type %temp% and enter. Look in there for the old nvda log. it will have old in its name. look upwards from the bottom in something like note pad to see what the error is, if there is one. However set the logging level to debug and that will ensure any log you get will have the maximum detail in it. If you do find errors etc, then save tat log to your doc folder to keep it safe and come back and maybe paste the important part to a message as there are people here who may be able to help resolve the issue. It could be lots of things, but I'd not want to speculate. Brian
bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field.
toggle quoted messageShow quoted text
----- Original Message ----- From: "Don H" <lmddh50@...> To: <nvda@nvda.groups.io> Sent: Monday, November 06, 2017 10:49 PM Subject: [nvda] NVDA crashing Running NVDA 2017-3 on a Win 10 64 bit Fall Creator edition laptop. On what seems to be a random thing on numerous occasions when I hit the windows key to open up the start menu NVDA simply goes away. I have no speech and hitting insert n to open the NVDA UI does nothing. Is there a way to capture what is happening to NVDA? Under the nvda tools menu view log only shows what I think is the restrt of NVDA when I start NVDA again with control alt n. Thanks
|
|
Here is what I get from debug. I guess that those oleacc.AccessibleObjects appear because I have pressed some keys on my keyboard while NVDA was frozen. But I might be wrong. So does anyone have a solution in mind? In addition, how can I make java access bridge available? And what is the user gesture map? DEBUG - core.main (23:14:26.414):
initializing Java Access Bridge support
WARNING - core.main (23:14:26.414):
Java Access Bridge not available
Â
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (23:14:26.848):
No user gesture map
Â
DEBUGWARNING - watchdog._watcher (23:14:37.453):
Trying to recover from freeze, core stack:
 File "nvda.pyw", line 199, in <module>
 File "core.pyo", line 396, in main
 File "wx\_core.pyo", line 8657, in MainLoop
 File "wx\_core.pyo", line 7952, in MainLoop
 File "core.pyo", line 366, in Notify
 File "IAccessibleHandler.pyo", line 889, in pumpAll
 File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
 File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
 File "_UIAHandler.pyo", line 314, in isUIAWindow
 File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
Â
WARNING - watchdog._watcher (23:14:52.469):
Core frozen in stack:
 File "nvda.pyw", line 199, in <module>
 File "core.pyo", line 396, in main
  File "wx\_core.pyo", line 8657, in MainLoop
 File "wx\_core.pyo", line 7952, in MainLoop
 File "core.pyo", line 366, in Notify
 File "IAccessibleHandler.pyo", line 889, in pumpAll
 File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
 File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
 File "_UIAHandler.pyo", line 314, in isUIAWindow
 File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
Â
WARNING - watchdog._watcher (23:15:07.484):
Core frozen in stack:
 File "nvda.pyw", line 199, in <module>
 File "core.pyo", line 396, in main
 File "wx\_core.pyo", line 8657, in MainLoop
 File "wx\_core.pyo", line 7952, in MainLoop
 File "core.pyo", line 366, in Notify
 File "IAccessibleHandler.pyo", line 889, in pumpAll
 File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
 File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
 File "_UIAHandler.pyo", line 314, in isUIAWindow
 File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
Â
WARNING - watchdog._watcher (23:15:22.500):
Core frozen in stack:
 File "nvda.pyw", line 199, in <module>
 File "core.pyo", line 396, in main
 File "wx\_core.pyo", line 8657, in MainLoop
 File "wx\_core.pyo", line 7952, in MainLoop
 File "core.pyo", line 366, in Notify
 File "IAccessibleHandler.pyo", line 889, in pumpAll
 File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
 File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
 File "_UIAHandler.pyo", line 314, in isUIAWindow
 File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
Â
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.316):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2124 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.318):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2125 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2126 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66130, objectID 109 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2134 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2135 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2136 and childID 0: [Error -2147467259] Unbekannter Fehler
Â
Thank you for your suggestions.
Best Adriani
|
|
Brian's Mail list account
I seem to have missed a lot of messages in this thread. What exactly are you doing to get this lock up? It seems to be attempting to read a screen which is not being recognised and getting into a loop.
Brian
bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field.
toggle quoted messageShow quoted text
----- Original Message ----- From: "adriani.botez via Groups.Io" <adriani.botez@...> To: <nvda@nvda.groups.io> Sent: Wednesday, November 08, 2017 10:42 PM Subject: Re: [nvda] NVDA crashing
Here is what I get from debug. I guess that those oleacc.AccessibleObjects appear because I have pressed some keys on my keyboard while NVDA was frozen. But I might be wrong. So does anyone have a solution in mind? In addition, how can I make java access bridge available? And what is the user gesture map?
DEBUG - core.main (23:14:26.414):
initializing Java Access Bridge support
WARNING - core.main (23:14:26.414):
Java Access Bridge not available
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (23:14:26.848):
No user gesture map
DEBUGWARNING - watchdog._watcher (23:14:37.453):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:14:52.469):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:07.484):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:22.500):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.316):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2124 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.318):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2125 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2126 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66130, objectID 109 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2134 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2135 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2136 and childID 0: [Error -2147467259] Unbekannter Fehler
Thank you for your suggestions.
Best Adriani
|
|
if you dont use java programs, you dont need to install java access briedge! hope that help, God bless you! On 11/9/17, Brian's Mail list account via Groups.Io <bglists@...> wrote: I seem to have missed a lot of messages in this thread. What exactly are you
doing to get this lock up? It seems to be attempting to read a screen which
is not being recognised and getting into a loop.
Brian
bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "adriani.botez via Groups.Io" <adriani.botez@...> To: <nvda@nvda.groups.io> Sent: Wednesday, November 08, 2017 10:42 PM Subject: Re: [nvda] NVDA crashing
Here is what I get from debug. I guess that those oleacc.AccessibleObjects appear because I have pressed some keys on my keyboard while NVDA was frozen. But I might be wrong. So does anyone have a solution in mind? In addition, how can I make java access bridge available? And what is the user
gesture map?
DEBUG - core.main (23:14:26.414):
initializing Java Access Bridge support
WARNING - core.main (23:14:26.414):
Java Access Bridge not available
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (23:14:26.848):
No user gesture map
DEBUGWARNING - watchdog._watcher (23:14:37.453):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:14:52.469):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:07.484):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:22.500):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.316):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2124 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.318):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2125 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2126 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66130, objectID 109 and childID
0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2134 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2135 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2136 and childID 0: [Error -2147467259] Unbekannter Fehler
Thank you for your suggestions.
Best Adriani
-- we have not sent you but as a mercy to the entire creation. holy quran, chapter 21, verse 107. in the very authentic narration from prophet Mohammad is: indeed, imam husayn is the beacon of guidance and the ark of salvation. best website for studying islamic book in different languages www.al-islam.org
|
|
Brian's Mail list account
And I believe there is now no bridge for 32 bit java and the new versions of 64 bit have issues with nvda. I saw some issues tickets on this yesterday. Brian
bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field.
toggle quoted messageShow quoted text
----- Original Message ----- From: "zahra" <nasrinkhaksar3@...> To: <nvda@nvda.groups.io> Sent: Thursday, November 09, 2017 9:39 AM Subject: Re: [nvda] NVDA crashing if you dont use java programs, you dont need to install java access briedge! hope that help, God bless you!
On 11/9/17, Brian's Mail list account via Groups.Io <bglists@...> wrote:
I seem to have missed a lot of messages in this thread. What exactly are you
doing to get this lock up? It seems to be attempting to read a screen which
is not being recognised and getting into a loop.
Brian
bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "adriani.botez via Groups.Io" <adriani.botez@...> To: <nvda@nvda.groups.io> Sent: Wednesday, November 08, 2017 10:42 PM Subject: Re: [nvda] NVDA crashing
Here is what I get from debug. I guess that those oleacc.AccessibleObjects appear because I have pressed some keys on my keyboard while NVDA was frozen. But I might be wrong. So does anyone have a solution in mind? In addition, how can I make java access bridge available? And what is the user
gesture map?
DEBUG - core.main (23:14:26.414):
initializing Java Access Bridge support
WARNING - core.main (23:14:26.414):
Java Access Bridge not available
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (23:14:26.848):
No user gesture map
DEBUGWARNING - watchdog._watcher (23:14:37.453):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:14:52.469):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:07.484):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:22.500):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.316):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2124 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.318):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2125 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2126 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66130, objectID 109 and childID
0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2134 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2135 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2136 and childID 0: [Error -2147467259] Unbekannter Fehler
Thank you for your suggestions.
Best Adriani
-- we have not sent you but as a mercy to the entire creation. holy quran, chapter 21, verse 107. in the very authentic narration from prophet Mohammad is: indeed, imam husayn is the beacon of guidance and the ark of salvation. best website for studying islamic book in different languages www.al-islam.org
|
|
It is all about nvda freezing when pressing windows key in windows 10.
Von meinem iPhone gesendet
toggle quoted messageShow quoted text
Am 09.11.2017 um 10:27 schrieb Brian's Mail list account via Groups.Io <bglists@...>:
I seem to have missed a lot of messages in this thread. What exactly are you doing to get this lock up? It seems to be attempting to read a screen which is not being recognised and getting into a loop.
Brian
bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "adriani.botez via Groups.Io" <adriani.botez@...> To: <nvda@nvda.groups.io> Sent: Wednesday, November 08, 2017 10:42 PM Subject: Re: [nvda] NVDA crashing
Here is what I get from debug. I guess that those oleacc.AccessibleObjects appear because I have pressed some keys on my keyboard while NVDA was frozen. But I might be wrong. So does anyone have a solution in mind? In addition, how can I make java access bridge available? And what is the user gesture map?
DEBUG - core.main (23:14:26.414):
initializing Java Access Bridge support
WARNING - core.main (23:14:26.414):
Java Access Bridge not available
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (23:14:26.848):
No user gesture map
DEBUGWARNING - watchdog._watcher (23:14:37.453):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:14:52.469):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:07.484):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:22.500):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.316):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2124 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.318):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2125 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2126 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66130, objectID 109 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2134 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2135 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2136 and childID 0: [Error -2147467259] Unbekannter Fehler
Thank you for your suggestions.
Best Adriani
|
|
I use java programs. Anyway, at least i could solve the java problem.
Von meinem iPhone gesendet
toggle quoted messageShow quoted text
Am 09.11.2017 um 10:39 schrieb zahra <nasrinkhaksar3@...>:
if you dont use java programs, you dont need to install java access briedge! hope that help, God bless you!
On 11/9/17, Brian's Mail list account via Groups.Io <bglists@...> wrote:
I seem to have missed a lot of messages in this thread. What exactly are you
doing to get this lock up? It seems to be attempting to read a screen which
is not being recognised and getting into a loop.
Brian
bglists@... Sent via blueyonder. Please address personal email to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "adriani.botez via Groups.Io" <adriani.botez@...> To: <nvda@nvda.groups.io> Sent: Wednesday, November 08, 2017 10:42 PM Subject: Re: [nvda] NVDA crashing
Here is what I get from debug. I guess that those oleacc.AccessibleObjects appear because I have pressed some keys on my keyboard while NVDA was frozen. But I might be wrong. So does anyone have a solution in mind? In addition, how can I make java access bridge available? And what is the user
gesture map?
DEBUG - core.main (23:14:26.414):
initializing Java Access Bridge support
WARNING - core.main (23:14:26.414):
Java Access Bridge not available
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (23:14:26.848):
No user gesture map
DEBUGWARNING - watchdog._watcher (23:14:37.453):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:14:52.469):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:07.484):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
WARNING - watchdog._watcher (23:15:22.500):
Core frozen in stack:
File "nvda.pyw", line 199, in <module>
File "core.pyo", line 396, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 366, in Notify
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent
File "IAccessibleHandler.pyo", line 523, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 314, in isUIAWindow
File "_UIAHandler.pyo", line 308, in _isUIAWindowHelper
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.316):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2124 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.318):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2125 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2126 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66130, objectID 109 and childID
0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2134 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2135 and childID 0: [Error -2147467259] Unbekannter Fehler
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):
oleacc.AccessibleObjectFromEvent with window 66140, objectID 2136 and childID 0: [Error -2147467259] Unbekannter Fehler
Thank you for your suggestions.
Best Adriani
-- we have not sent you but as a mercy to the entire creation. holy quran, chapter 21, verse 107. in the very authentic narration from prophet Mohammad is: indeed, imam husayn is the beacon of guidance and the ark of salvation. best website for studying islamic book in different languages www.al-islam.org
|
|