Outlook crash navigating by line
|
Sally Kiebdaj
Hello all, Could you help me figure out how to properly report a problem? When navigating in outlook by line, if I find an embedded graphic outlook crashes. NVDA continues running and outlook usually restarts automatically. However, having it crash unexpectedly is never ideal. Has anyone else seen this? Since it appears to be an outlook problem, are there windows or outlook logs I should be looking at? NVDA logs do seem to show some kind of an error with UIA: ERROR - scriptHandler.executeScript (11:06:32.220) - MainThread (19604): error executing script: <bound method CursorManager.script_moveByLine_forward of <NVDAObjects.UIA.wordDocument.WordBrowseModeDocument object at 0x09E8EE10>> with gesture 'down arrow' Traceback (most recent call last): File "NVDAObjects\UIA\__init__.pyc", line 427, in __init__ File "monkeyPatches\comtypesMonkeyPatches.pyc", line 32, in __call__ _ctypes.COMError: (-2147220991, 'An event was unable to invoke any of the subscribers', (None, None, None, 0, None)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "scriptHandler.pyc", line 257, in executeScript File "cursorManager.pyc", line 256, in script_moveByLine_forward File "cursorManager.pyc", line 129, in _caretMovementScriptHelper File "documentBase.pyc", line 61, in makeTextInfo File "treeInterceptorHandler.pyc", line 179, in __init__ File "NVDAObjects\UIA\__init__.pyc", line 429, in __init__ RuntimeError: No selection available ERROR - RPC process 12644 (nvda_slave.exe) (11:06:36.858) - Dummy-5 (21028): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 119, in main File "comHelper.pyc", line 22, in _lresultFromGetActiveObject File "comtypes\client\__init__.pyc", line 180, in GetActiveObject File "comtypes\__init__.pyc", line 1285, in GetActiveObject File "_ctypes/callproc.c", line 935, in GetResult OSError: [WinError -2147221021] Operation unavailable If I am using the read to end command, graphics do not crash outlook. Any thoughts on how to best report this since it primarily impacts outlook? The environment is: Windows Version 21H2 (OS Build 19044.2130) Microsoft® Outlook® 2019 MSO (16.0.10392.20029) 64-bit NVDA Version: 2022.3.2 Warmly, Sally |
|
|
|
Gene
I suspect, from what you say that this is an NVDA problem. While I
don't have the technical knowledge to discuss the problem to any
extent, one way to see whether NVDA is causing the crashes is to do
what you do using Narrator or JAWS.
toggle quoted message
Show quoted text
As far as reporting the problem, I'll let others discuss that. I can do so on Github, but I look around to see just what to do. I haven't done so enough to have organized knowledge I can write without going through most of the procedure again. Others likely do. Gene On 11/15/2022 4:17 AM, Sally Kiebdaj
wrote:
|
|
|
|
Hi, In addition to sending a debug log to NV Access (info@...), try after restarting with add-ons disabled. The error fragment sounds like NVDA wants something from Outlook as reported by UI Automation but somehow it doesn't go through. The line that says "an event was unable to invoke any of its subscribers" is encountered when NVDA does not realize that the app you were using has crashed and still thinks it can get something from the app. The second line "operation unavailable" indicates that NVDA was trying to get something from Outlook without realizing that the operation isn't supported in older Outlook versions. Based on the log fragment and the version of Outlook reported, it looks like somehow NVDA is told to use UI Automation to access Microsoft Word documents. This works better with later Outlook releases, specifically in build 16.0.13901 and later. Note that Outlook may embed a Microsoft Word document control when displaying email content, and if NVDA is told to use UIA to access Word, NVDA will rely on UI Automation when you read email messages. I think this is as far as I can go when it comes to explaining the traceback to users. Cheers, Joseph |
|
|
|
Sally Kiebdaj
Thank you! So I can preliminarily confirm this is an NVDA issue with UIA. Several releases ago, I had to change the advanced setting "Use UI Automation to access Microsoft Word document controls" to "always". As an experiment, I set it back to "Where suitable" and now outlook does not crash. We'll see how comments in word behave with this change but at least now I know how to toggle this setting to use comments in word and see graphics in outlook, as needed. Do you think I should still report this or is it edge enough with an old enough version of outlook to not be worth developers' time? Warmly, Sally On Tue, Nov 15, 2022 at 11:56 AM Joseph Lee <joseph.lee22590@...> wrote:
|
|
|
|
Hi, This issue is more towards a combination of Outlook and NVDA: Outlook because UIA implementation is not that solid in older releases, and NVDA since it doesn't support older Outlook releases as far as UIA support is concerned (more towards Microsoft Word really). This is reflected in NVDA's own source code which states that UIA support is usable with Microsoft 365 build 16.0.13901 and later (released a year or so ago). I would put more emphasis on Outlook based on NVDA source code statement. As for what NVDA developers will do with it, I don't know for sure (as I don't work for NV Access), but I think at this point they might ask you to update to a newer Microsoft 365 or Office 2021 release (I do see that you've got Office 2019 activated with a volume license key; source: Office security updates release notes). I doubt developers will do anything with it at this point. Cheers, Joseph |
|
|
|
Sally Kiebdaj
Hello, I figured that might be the case. As the license is for work and institution wide, I doubt I can push for any updates. The strange thing to me is that I need two different settings within the same "generation" of office in order to work with word and outlook. It seems that office is quite internally inconsistent, in that respect. Thanks for helping me find a work around! warmly, Sally On Tue, Nov 15, 2022 at 3:28 PM Joseph Lee <joseph.lee22590@...> wrote:
|
|
|
|
Brian's Mail list account
I had a similar error recently when I was using Waterfox It looked like Waterfox went away, but NVDA still thought it was doing something and then found it could not.
toggle quoted message
Show quoted text
Its so random, its hard to pin it down, but Outlook is a different problem as so many use it. Brian -- bglists@... Sent via blueyonder.(Virgin media) Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message -----
From: "Gene" <gsasner@...> To: <nvda@nvda.groups.io> Sent: Tuesday, November 15, 2022 10:29 AM Subject: Re: [nvda] Outlook crash navigating by line I suspect, from what you say that this is an NVDA problem. While I |
|
|
|
Brian's Mail list account
I notice that many vendors of computers are now bundling free licences of Office 2019 with their machines, so I'd imagine the issue will only get worse before it gets better, as 2019 is not very long ago, after all.
toggle quoted message
Show quoted text
Brian -- bglists@... Sent via blueyonder.(Virgin media) Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...> To: <nvda@nvda.groups.io> Sent: Tuesday, November 15, 2022 2:28 PM Subject: Re: [nvda] Outlook crash navigating by line Hi, This issue is more towards a combination of Outlook and NVDA: Outlook because UIA implementation is not that solid in older releases, and NVDA since it doesn't support older Outlook releases as far as UIA support is concerned (more towards Microsoft Word really). This is reflected in NVDA's own source code which states that UIA support is usable with Microsoft 365 build 16.0.13901 and later (released a year or so ago). I would put more emphasis on Outlook based on NVDA source code statement. As for what NVDA developers will do with it, I don't know for sure (as I don't work for NV Access), but I think at this point they might ask you to update to a newer Microsoft 365 or Office 2021 release (I do see that you've got Office 2019 activated with a volume license key; source: Office security updates release notes). I doubt developers will do anything with it at this point. Cheers, Joseph |
|
|
|
Brian's Mail list account
Could this particular toggle be set up as a triggered set up change depending on the executable name as we can do with other things in nvda?
toggle quoted message
Show quoted text
Brian -- bglists@... Sent via blueyonder.(Virgin media) Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message -----
From: "Sally Kiebdaj" <fiddle.pup@...> To: <nvda@nvda.groups.io> Sent: Tuesday, November 15, 2022 10:10 PM Subject: Re: [nvda] Outlook crash navigating by line Hello, |
|
|