Running version 7.5.3.2 then 7.5.5.2 Linux Mint 20.1 5.4.0-153-generic 64bit I wrote a simple test Writer document with a nonsense word on each line: This is my abcdef test document ghijk with deliberate errors lmnop for adding to a dictionary. 1: I clicked the spellchekck button with the cursor at the start of the document. 2: I created a new dictionary (SpellCheckBugTestDictionary) click Options, then New 3: "abcdef" was highlighted as a spell error and I added that to SpellCheckBugTestDictionary using the drop-down list 4: "ghijk" was highlighted as a spell error BUT with most of the dialog greyed out and the top-most button set to "Resume" - this is not behaviour I would expect. 5: I clicked on "Resume" 6: I added "ghijk" to SpellCheckBugTestDictionary using the drop-down list 7: I immediately got a dialog "Continue checking at beginning of document". (Checking later, "ghijk" had been added to the dictionary) 8: I clicked yes. 9: I immediately got a dialog "The spellcheck is complete", which is not correct because there is still the error in the third line The spellcheck dialog remained open, still showing "ghijk" as mis-spelled with no option to move on other than by "correcting" the word or closing the spellchecker 10: When I closed and re-started the spellchecker, it correctly picked up on the error in the third line "lmnop" 11: I repeated the test sequence and selected "Correct" at the end of step 9, when it told me that the spellcheck was complete. The text in the spellcheck dialog was modified to "document ghijk with deliberatehijack", "hijack" being the top suggestion to correct "ghijk", so the spellchecker is clearly in an anomalous state at this point. The text in the document was not modified.
Thank you for reporting the bug. I can not reproduce the bug in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: en-US Calc: threaded Steps 4-5 were not reproduced for me. I successfully added "ghijk" to the dictionary with the dialog greying out and the top "Resume" button appearing. Steps 7-10 were also not reproduced for me. I successfully added the error in the third line (lmnop) to the dictionary and only then the dialog "The spell check is complete" appears. However, the behaviour after this is a little unexpected. After I closed the "The spell check is complete" dialog, the word "lmnop" is no longer marked as an error in the document but in the white space area between "Not in Dictionary" and "Suggestions", it's still marked as an error. It's only when I restart the spell check then everything is fine and it shows there are no errors as expected. That seems to be the only incorrect behaviour I've found from my end.
I don't know whether this should remain as a bug, but quite by chance I seem to have fixed it on my laptop when I was trying to fix something else. When I let LibreOffice open normally, the mouse cursor is offset from the text cursor position. This led me to a suggested fix of launching with "SAL_USE_VCLPLUGIN=gen" which fixed the mouse problem and the spellcheck issue. When my system does the normal LO open, I see the rendering as "default; VCL: gtk3" but with "SAL_USE_VCLPLUGIN=gen" I get "default; VCL: x11". I also tried the option "SAL_USE_VCLPLUGIN=kf5" which also resolved both the spellcheck and mouse position issues. I'm not sure whether that makes this a gtk bug or a LibreOffice bug.
Repro with gtk3. Already in oldest of Linux 6.0 repo, so probably always this way. Arch Linux 64-bit, X11 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 43df1237a091e2b0f4495d5a7e959f7beaab025d CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 13 September 2023
Dear Mark Huntley-James, 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