Description: the moment LibreOffice 6.3.0.4 was installed, I mean, Writer, I saw that something was wrong, the behavior of the spell checker changed... it was just hard to catch what this change was exactly... generally, I experienced that it was slow, even lagging, that is, showing the results only ONE PHASE later... not when you would expect it... by "showing the results" I mean, underlining a word or removing the underlining... (due to correction)... Steps to Reproduce: 1. write sdfsdfsdfsdfds 2. hit space 3. Actual Results: sometimes it is NOT underlined... then you hit space again, and then it would be underlined... right now I have a document in which in one paragraph I can hit space once and the underlining appears promptly, but one paragraph above, I write "fgdfgdgdfgdf" then hit space, and nothing happens. one more piece of info: now I closed that document... reopened it... and in the erroneous paragraph above the good one, there is NO underlining.. + one more: I copy-pasted these two paragraphs into a new document, and both paragraphs work fine... - - - another version of this behavior is that as I'm writing, there are underlined words above where I am, and they are already correct... but still underlined... so I will go there, try to check them, try to correct them, but find that they are already correct... and then I'll have to place the cursor after them and hit space... Expected Results: when I correct a word, it should be underlined or cleared at the next keyboard hit.. Reproducible: Always User Profile Reset: No Additional Info: this behavior appeared right after installing version 6.3.0.4... and I run into it every time... - - - Version: 6.3.0.4 Build ID: 1:6.3.0-0ubuntu0.18.04.1~lo2 CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded --------------------------------- [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
ONE more example of this behavior: 1. you write docuumentary 2. move on... do whatever until it is underlined... 3. place the cursor at "u" and hit backspace... what happens: the underlining doesn't disappear it will only disappear when you place the cursor after the word (for example) and hit space or anything)... that is, +1 keystroke...
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
I've reseted the user profile and the issue appears to be GONE. sorry for not doing this first :( and thanks! Peter
sorry, the issue is NOT GONE completely... one example: I just saw the word "up" underlined as wrong spelling... and I had to put the cursor next to it, and hit space, so it would disappear.. this incident has not been the only one since (30 minutes ago) I thought it was all gone... this was the last straw :) I'll try to observe it more carefully... once again, the problem is that underlining should dis/appear in real time, not with a lag... say, as you change appple to apple, underlining should disappear right away... whereas with changing apple to apple, we DO expect a lag, CAUSE the application needs to know that you have finished with typing your word :) this is what we can call the normal behavior, I suppose... this is how Mozilla firefox's spellchecker works, for example... and this is how Libreoffice Writer's used to work, allways.. until recently.. I'll report back soon...
sorry for the status overwriting!!! :)
Peter, unfortunately nothing has happened with this bug report for more than half year. So I'd like to ask, if it is still valid, because a new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. If it's still present, please update the steps to reproduce, because as far as I understood, the behaviour you described in comment 4 is a bit different than the behaviour in your initial bug report. Thanks.
Maybe related to bug 136294?
Dear peter josvai, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
*** Bug 124603 has been marked as a duplicate of this bug. ***
Dear peter josvai, 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