Steps to reproduce: 1. Open a file containing data. (I tried xlsx and xls.) 2. Press Control+s to save the file. 3. Select use XLS or XLSX in the Confirm Format dialog. 4. The program crashes most of the time. It seems like once in a while the program doesn't crash and I am returned to the spreadsheet but for me the crash occurs much more frequently. I am adding accessibility to this in the hopes that someone can confirm whether this crash also occurs when accessibility is disabled. I tested with NVDA 2016.3 and Windows 10.
I forgot to add that this crash doesn't occur if Warn When not Saving in ODF or Default Format is unchecked in Options>Load/Save>General
It could be useful you retrieve a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Did you try with the NVDA screen reader enabled? You can download this from www.nvda-project.org and it is free and open source. I tried deleting my user profile for LibreOffice and I can still reproduce this bug.
Wasnt able to reproduce this with Orca 3.20 or NVDA 2016.3. If this happens on a particular xls or xlsx file, please submit it so we can test against it. Would assume this isnt a11y related. If you are able to reproduce the crash on libreoffice 5.2.1, then after it crashes, libreoffice will prompt you to send in a crash report, so please do so and then we'll be able to track down the issue. Version: 5.3.0.0.alpha0+ Build ID: 78404fe5549fded2eaf0c5ea6e1ca66039e995af CPU Threads: 2; OS Version: Linux 3.19; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-09-11_09:14:01 Locale: en-US (en_US.UTF-8); Calc: group
The crash doesn't occur in the 5.2 version. I had someone sightred test with NVDA disabled on this Windows machine and the crash does not occur in the 5.3 version. The key to causing the crash in nVDA for me is ensuring that an existing document is used. The crash will not occur if it is the first save of a new document. The crash even occurrs if I save a spreadsheet with the text test in cell aq and then close and reopen that and save it.
Which windows version are you using? Can you ask the sighted person to test 5.3 with NVDA and see if they can confirm it? If he/she is able to confirm it, ask them to follow the instructions below to obtain a backtrace. https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Using STR I confirm crash on Windows 10 Pro 64-bit en-US (v.1607) with NVDA 2016.3 and LibreOffice master Version: 5.3.0.0.alpha0+ Build ID: 681d5fd37e469491268d40147c621187dc6f4b95 CPU Threads: 8; OS Version: Windows 6.19; UI Render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2016-09-10_06:06:09 Locale: en-US (en_US); Calc: group attempt to check with TB39 that should have symbols available. Version: 5.3.0.0.alpha0+ Build ID: d5fab973d0af95c433c5f6a9492014f7db642489 CPU Threads: 8; OS Version: Windows 6.19; UI Render: GL; TinderBox: Win-x86@39, Branch:master, Time: 2016-08-24_00:07:50 Locale: en-US (en_US); Calc: CL But, seems NVDA 2016.3 on Windows 10 Pro "anniversary update", e.g. ver 1607 is not especially stable. NVDA freezes all reading activity when attempting to open LibreOffice. @Jamie, Mick -- any insight?
Opened an NVACCESS issue against NVDA https://github.com/nvaccess/nvda/issues/6385
The Windows computers that I have access to were downgraded to Windows 7 due to software incompatibilities. I can confirm that the issue did occur with NVDA before and after the Anniversary update. It does not occur in Windows 7 which I tested after the machines were downgraded. I can't do any further testing on this issue in Windows 10 because I do not personally own any Windows computers.
I am not able to reproduce this on my personal laptop with Orca that runs BSD.
Dear all, It looks like it is a Windows specific issue. I move the a11y tag to a11y-Windows and change the targeted platform. Best regards.
About NVDA, https://github.com/nvaccess/nvda/issues/6385 has been closed. another bugtracker https://github.com/nvaccess/nvda/issues/7631 had been opened and finally closed. Any better with last stable LO version 5.4.4 + last stable nvda 2017.4 ? As usual, if someone still reproduces this, a debug bt could be useful
(In reply to Julien Nabet from comment #12) > About NVDA, https://github.com/nvaccess/nvda/issues/6385 has been closed. > another bugtracker https://github.com/nvaccess/nvda/issues/7631 had been > opened and finally closed. > > Any better with last stable LO version 5.4.4 + last stable nvda 2017.4 ? > As usual, if someone still reproduces this, a debug bt could be useful @Alex ARNAUD, @V Stuart Foote, Do you still reproduce this issue in 5.4.4 and the latest stable verion of nvda ?
(In reply to Xisco Faulí from comment #13) > @Alex ARNAUD, @V Stuart Foote, Do you still reproduce this issue in 5.4.4 > and the latest stable verion of nvda ? With NVDA 2017.3 on Windows 10 Enterprise 64-bit en-US--no issues with 6.0.0.3, nor with /a admin installs of 5.4.4.2 or 6.1.0alpha1+ master. => WFM