Download it now!
Bug 101906 - Crash on exit when using JAWS screen reader
Summary: Crash on exit when using JAWS screen reader
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks: a11y-Windows
  Show dependency treegraph
 
Reported: 2016-09-05 13:29 UTC by Yousuf Philips (jay) (retired)
Modified: 2019-06-29 02:59 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
backtrace (77.66 KB, text/plain)
2017-11-04 19:49 UTC, Yousuf Philips (jay) (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2016-09-05 13:29:20 UTC
Steps:
1) Start JAWS
2) Open Writer
3) Close LO
4) Windows opens a 'LO has stopped working' dialog saying the faulty module name is vcllo.dll

Tested on Windows 7 with 5.3 master x86@42 from 08-29
Comment 1 Yousuf Philips (jay) (retired) 2016-09-21 01:08:49 UTC
Crashes on 5.2.1 as well but doesnt startup afterwards to send in backtrace to server.

@Stuart, @am_dxer: you by chance have JAWS or know someone with it?
Comment 2 V Stuart Foote 2016-09-21 04:27:02 UTC
(In reply to Yousuf Philips (jay) from comment #1)
> Crashes on 5.2.1 as well but doesnt startup afterwards to send in backtrace
> to server.
> 
> @Stuart, @am_dxer: you by chance have JAWS or know someone with it?

Sorry, no seat of JAWS. I'll have to check with our Accessibility services folks to find a system that I can get sysadmin permissions on and set up WinDbg and a LibreOffice install.

Of course with no Symbols--not sure how useful the StackTrace would be.

@Kendy, can you give TB39 a nudge?
Comment 3 Chris Sherlock 2017-03-11 06:22:04 UTC
How does JAWS interact with LO?
Comment 4 Xisco Faulí 2017-03-14 09:17:47 UTC
Hi Yousuf,
Could you please obtain a backtrace for the crash?
Comment 5 Xisco Faulí 2017-11-02 10:20:50 UTC
(In reply to Xisco Faulí from comment #4)
> Hi Yousuf,
> Could you please obtain a backtrace for the crash?

Hi Jay,
Any update here?
Comment 6 Yousuf Philips (jay) (retired) 2017-11-04 19:49:15 UTC
Created attachment 137524 [details]
backtrace

(In reply to Xisco Faulí from comment #5)
> Any update here?

Here is a backtrace from 5.4.2 and Jaws 17.
Comment 7 Xisco Faulí 2018-11-27 12:56:04 UTC
hello Jay,
is this issue still reproducible in master ?
Comment 8 daniel 2018-11-29 04:10:21 UTC
Bug not reproducible in version.Version:6.3.Hardware:all
Comment 9 Xisco Faulí 2018-11-29 09:22:46 UTC
(In reply to daniel from comment #8)
> Bug not reproducible in version.Version:6.3.Hardware:all

Hello Jay,
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
Comment 10 QA Administrators 2019-05-29 02:53:38 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2019-06-29 02:59:22 UTC
Dear Yousuf Philips (jay) (retired),

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp