I open a fresh Calc session or an existing (small document), then, whatever I do, whatever I try to type, I have to wait for 8-15 seconds to see the results; since I blindly type (no feedback in the white cell), I try to also correct, so I double click the cell, wait those seconds, edit, press enter, then wait those 8-15 seconds and so on. I had this issue with probably all versions after 7.0.1 (the one I installed now fresh from your archive on the site). I found several recommendations in the libreoffice community, but nothing worked. Can you help me with this? My Ubuntu Studio Linux version does not have this problem. Please let me know if you need any other information. I am ready to install again the latest version and follow your advices. I uninstall using IoBit Uninstaller, for a complete uninstall. Thank you.
Please write here the info from LibreOffice's Help->About dialog (use a Copy button there)
Bug 144612 reported that there is a lag/slowness when typing in a cell, but it was broken since 7.2 and worked OK in previous versions (7.0, 7.1 etc). However, in THIS report you stated that you had this issue in all versions after 7.0. Please clarify, does it work in 7.0? does it work in 7.1? How about 7.2 and 7.3? Also please provide the info as requested in comment 1, thanks.
First of all, thank you for your reply! Secondly, I need to appologize because I am in a bit of a crisis here and I can't aford right now to go back and forward between various versions of the program, I need to use it daily even more than I actually do, if you could get my point... So, all I can do now is provide at least the info in the Help/About window, in a realible manner, as you professionally suggested in comment 1. Here it is: Version: 7.0.6.2 (x64) Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL As soon as I will be able to move a bit more freely around, I will test more, as you suggested in your comments. Thank you again for all your efforts and your precious help!
Of course, this, 7.0.6.2 (x64), is the functional version I am using now.
[Automated Action] NeedInfo-To-Unconfirmed
Not clear again, unfortunately. You didn't say exactly in which version you last saw a lag. Do you say that 7.0.6.2 is OK? Question is: is 7.1.8 OK or not or you - save for small lag on 1st type as in https://bugs.documentfoundation.org/show_bug.cgi?id=144612#c0? No point in separating reports, especially for a bug like this which is not normally reproducible. So if 7.1.8 is OK and 7.2 is not, it should be duplicated to earlier report. Normally, before report you should've searched. That's why we have form when reporting bugs, use https://bugs.documentfoundation.org/enter_bug.cgi and not mail report or how you avoded that form.
I appologize for any inconvenience I caused and any waste of time in processing my bug report. I will install successive versions of the software and trace the bug, then come back to you. I am not sure what version of the software I used when I encountered the errors, it was the last version available on site at that date, but, again, you are not expected to do software archeology here... Thank you again, I will come back in a month or so, when I will be able to fulfil the requirements for such a bug report. Until then, I canceled all updates and I will keep using this version 7.0.6.2 (x64) which is functional for me. Thank you!
(In reply to adrian.vidrascu from comment #7) Actually you do not need to install and uninstall each of the prior versions. There is a more accurate and convenient way to do so, which is called "bibisect", see: https://wiki.documentfoundation.org/QA/Bibisect. To bibisect, you need to know some git skills, but all of these are detailed on the wiki page, thus it not that hard to follow. The bibisect repository for windows can be found in: https://wiki.documentfoundation.org/QA/Bibisect/Windows and for Linux, it is: https://wiki.documentfoundation.org/QA/Bibisect/Linux With a successful bibisect, we will know which exact commit has caused this regression, and proceed accordingly.
(In reply to Roman Kuznetsov from comment #1) > Please write here the info from LibreOffice's Help->About dialog (use a Copy > button there) Version: 7.2.5.2 (x64) / LibreOffice Community Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL I reinstalled the latest version and check the behaviour, it is the same as I reported. Again, this is on a Windows 10, 64 bit machine, Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz 3.70 GHz, 8 GB RAM, 64-bit operating system, x64-based processor, running Windows 10 Home edition, version 21H1 (updating now further), Windows Feature Experience Pack 120.2212.3920.0.
This bug is already too long without significant info. I'll assume it's a duplicate. *** This bug has been marked as a duplicate of bug 144612 ***