Topics

And finally, for now.

Brian's Mail list account
 

OK then what about this little problem on another windows 7 machine?



Hi folks. I just installed the 3 try version of nvda to stop the explorer crash in windows 7, and of course its too early to tell the outcome of that. However when Windows 7 Home Premium boots up it firstly takes a long time, 11 seconds according to the log, even though the same settings and add ons here at home do not have any issues. Here are the parts of the log that look like issues.

Initializing UIA support
DEBUGWARNING - RPC process 1824 (dwm.exe) (13:01:53.380):
Thread 3364, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 66:
SetWindowsHookEx with WH_GETMESSAGE failed, GetLastError returned 5

DEBUGWARNING - RPC process 1824 (dwm.exe) (13:01:53.381):
Thread 3364, build\x86_64\remote\injection.cpp, inproc_winEventCallback, 69:
SetWindowsHookEx with WH_CALLWNDPROC failed, GetLastError returned 5

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:01:53.629):
UIAutomation: IUIAutomation
DEBUG - core.main (13:01:55.351):

snip
NVDA initialized
DEBUG - core.main (13:01:58.660):
entering wx application main loop
DEBUGWARNING - watchdog._watcher (13:01:59.332):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 221, in <module>
File "core.pyc", line 536, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui\__init__.pyc", line 997, in Notify
File "core.pyc", line 505, in run
File "IAccessibleHandler.pyc", line 901, in pumpAll
File "IAccessibleHandler.pyc", line 624, in processGenericWinEvent
File "IAccessibleHandler.pyc", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyc", line 42, in getNVDAObjectFromEvent
File "IAccessibleHandler.pyc", line 342, in accessibleObjectFromEvent
File "oleacc.pyc", line 265, in AccessibleObjectFromEvent

DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (13:01:59.472):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
IO - speech.speak (13:01:59.529):
Speaking [LangChangeCommand ('en_GB'), 'NVDA']
IO - inputCore.InputManager.executeGesture (13:02:07.047):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:07.431):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:07.767):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:08.023):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:08.279):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:11.087):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:11.439):
Input: kb(desktop):upArrow
IO - inputCore.InputManager.executeGesture (13:02:11.734):
Input: kb(desktop):downArrow
IO - inputCore.InputManager.executeGesture (13:02:13.415):
Input: kb(desktop):alt+tab
IO - speech.speak (13:02:13.900):
Speaking [LangChangeCommand ('en_GB'), 'Desktop icon 2 of 2']
IO - speech.speak (13:02:14.174):
Speaking [LangChangeCommand ('en_GB'), 'FolderView list']

As you will note we have the guest appearence of a very old problem from the past, a blank nvda window focussed after boot up of the machine. If I then reboot nvda things seem to work as normal.
Is this a problem that anyone else has had, could it be a windows issue??
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Leonard de Ruijter" <@leonardder>
To: <nvda-devel@groups.io>
Sent: Thursday, August 29, 2019 8:23 AM
Subject: Re: [nvda-devel] And finally, for now.


They have been introduced by the vision framework, I added some
additional debug statements to the window creation there. Nothing to
worry about. These issues were already there, they just weren't logged.


 

They have been introduced by the vision framework, I added some additional debug statements to the window creation there. Nothing to worry about. These issues were already there, they just weren't logged.

Brian's Mail list account
 

On the log produced by the python 3 snapshot we have some log entries near the start which are odd.
DEBUG - windowUtils._rawWindowProc (08:00:49.894):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - windowUtils._rawWindowProc (08:00:49.894):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - windowUtils._rawWindowProc (08:00:49.894):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - windowUtils._rawWindowProc (08:00:49.895):
CustomWindow rawWindowProc called for unknown window 262472
DEBUG - core.main (08:00:49.897):
etc.
JUst wondered what they were.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users