Description: spelling check is reporting to user that spelling check has been completed when in fact spelling check has not been completed. The user is led to believe that the document has no spelling errors, but in fact the document might have spelling errors. This bug happens in Windows 10 and also Linux Mint a screen video of the bug in action https://youtu.be/JKG0-7FjLcc Steps to Reproduce: 1) Have several LibreOffice Writer documents open simultaneously... 2) It may or may not help reproduce the bug if some of the documents are new documents not saved to disk. 3) run a spell check in one of the documents. Continue with the spell check until you get the dialog window saying "The spellcheck is complete." Leave this dialog window open. Do not click "ok" on it. 4) switch to a different LibreOffice Writer document 5) run a spell check in the different LibreOffice Writer document 6) You will observe that the spell check now fails to find any spelling errors in any other LibreOffice Writer documents. The spell check reports in error that "The spellcheck is complete" when in fact the spellcheck has not been run. 7) Note that to get the bug to trigger you may have to switch back and forth a couple times between windows, maybe click off the spell check dialog to shift focus or some such. Actual Results: spelling check is reporting to user that spelling check has been completed when in fact spelling check has not been completed. The user is led to believe that the document has no spelling errors, but in fact the document might have spelling errors. Expected Results: tell me about my terrible spelling Reproducible: Sometimes User Profile Reset: No Additional Info: a screen video of the bug in action https://youtu.be/JKG0-7FjLcc I am pretty sure I remember this bug from years ago, so I think this bug has been present for quite a while. I have observed this bug in the following two versions: Version: 6.4.7.2 (x64) Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL Version: 6.1.5.2 Build ID: 90f8dcf33c87b3705e78202e3df5142b201bd805 CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group threaded
I have discovered that this bug seems to be triggered only when SELECT-ALL is performed immediately before the spell check of the first document. Thereafter, spell check of all other documents will fail as described in the bug.
In context of SELECT-ALL triggering this bug, (Reproducible: Sometimes) should be changed to (Reproducible: Always)
See my comments in https://bugs.documentfoundation.org/show_bug.cgi?id=138815 Spellcheck became unusable for Linux starting from a release candidate in Dec 2020. Noticing that someone has produced a YT video, that may be a way to show the problems I've described. Spellcheck broke so badly the feature became effectively unusable.
I reported a few versions ago that Auto Spellchecking was not finding misspelled words. Auto Spellchecking has been working fine in the most recent 6.* version I have been using. I just upgraded to version 7.1.6.2 and Auto Spellcheck is not finding any errors that I am making intentionally in order to test it (after I discovered one accidentally misspelled work that Auto Spellchecking did not find). Running on most recent version of Win 10.
No repro in Linux Mint 20: Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear antifascist, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug