Description: They are problems with LibrOffice Writer in Windows 11. We are from a computer store and have this problems on all new computers. When you install LibreOffice 7.2 or above the Writer program types verry slow. The charecters comes 3 to 10 seconds after the typing. So it's difficult for typing, and the Writer is just for typing. What i have tested: - New installation of Windows 11 with only Windows, the drivers and LibreOffice: Problem of slow typing - Installations of LibreOffice on more than 10 computers or laptops with Windows 11: allways the same problem. - Installation on Windows 10: no slow typing, no problems at all This are the versions i have tested: Libreoffice 7.1.3.2 on Windows 10 Works perfectly Libreoffice 7.2.3.2 on Windows 10 Works perfectly Libreoffice 7.1.3.2 on Windows 11 Works not good, slow typing Libreoffice 7.2.3.2 on Windows 11 Works not good, slow typing Libreoffice 7.0.2.1 on Windows 11 Works perfectly Libreoffice 6.4.7.2 on Windows 11 Works perfectly Steps to Reproduce: 1. The only thing that's work is install a older version of LibreOffice 2. Delete user profile doesn't work: same problem 3. Enable of disable openGL, java and other things: same problem Actual Results: I don't know how you can fixed. The only solution is install a old version Expected Results: Nothing, the problem is still the same Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: It must be fixed, we are from a computer store and install normally always LibreOffice, but when these problems are note fixed we must use a other program. We have also tested: OnlyOffice and freeoffice. With this programs there is no problem.
Tools -> Options -> View > Check force skia raster & press OK and restart? Does this improve the situation?
No i have already tested. Same slow typing problem.
Note: The error message was caused by this question in AskLibreOffice: https://ask.libreoffice.org/t/slow-typing-with-writer-in-windows-11/71028
*** Bug 146059 has been marked as a duplicate of this bug. ***
*** Bug 145761 has been marked as a duplicate of this bug. ***
I set New by duplicates. It's Major issue, I mark so, we don't have to wait dozen of reports to see a problem. By report is a regression. There's another bug for Calc. Reporter, to be sure but it's still valid, please test with LO master that's 7.4+ now, installing additional development version from https://dev-builds.libreoffice.org/daily/master/current.html
(In reply to Timur from comment #6) > I set New by duplicates. It's Major issue, I mark so, we don't have to wait > dozen of reports to see a problem. By report is a regression. There's > another bug for Calc. > > Reporter, to be sure but it's still valid, please test with LO master that's > 7.4+ now, installing additional development version from > https://dev-builds.libreoffice.org/daily/master/current.html I have also tested the new development version, but they have the same slow typing problem. With the old 7.0.x version it works fine, but not with the newer versions.
Everything is smooth in 7.1b1
@QA Bibisect can also be done on a VM: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
Created attachment 176929 [details] Bibisect log Bisected to author Luboš Luňák <l.lunak@centrum.cz> 2021-02-10 16:37:17 +0000 committer Luboš Luňák <l.lunak@collabora.com> 2021-02-11 11:07:11 +0100 commit 843af72bcc9047867588e29c8e10b84a5e58d70e (patch) tree 88c9412c20260832e905461df59e7ea9b7009805 parent ab882c0506c886eb32d8de0d2441de94920598bc (diff) make win32 variant AnyInput() not deliver events (tdf#140293) Win32 API PeekMessage() actually may deliver events, despite what the name may suggest, even with PM_NOREMOVE argument. That means this is problematic for use in AnyInput(), as that function should just check the event queue but not do anything with it. Using GetQueueStatus() should solve the problem. See https://lists.freedesktop.org/archives/libreoffice/2021-February/086788.html for further details. https://cgit.freedesktop.org/libreoffice/core/commit/?id=843af72bcc9047867588e29c8e10b84a5e58d70e
Adding CC: to Luboš Luňák Bumping to highest, because LibO being unusable on Windows 11.
(In reply to Telesto from comment #11) > Adding CC: to Luboš Luňák > > Bumping to highest, because LibO being unusable on Windows 11. I don't have Windows 11. Could you give me a CPU profile from the Diagnostic Tools in Visual Studio to possibly point to where the code is slow?
(In reply to Luboš Luňák from comment #12) > (In reply to Telesto from comment #11) > > Adding CC: to Luboš Luňák > > > > Bumping to highest, because LibO being unusable on Windows 11. > > I don't have Windows 11. Well you you're in luck. You can use Microsoft Windows 11 Enterprise (Developer Edition) virtual machine for for free. Visual studio and such pre-installed :-). Only limitation is time-trail 09/2022. https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/ > Could you give me a CPU profile from the Diagnostic Tools in Visual Studio to possibly point to where the code is slow? Will try, but does it give enough information with an ordinary daily build?
(In reply to Telesto from comment #13) > Will try, but does it give enough information with an ordinary daily build? I think it would need (debug) symbols, which I don't know if are included with dailies. But if there's a VM then I can test it myself.
Windows debug symbols are published for TDF releases, see <https://wiki.documentfoundation.org/Development/How_to_debug#Debugging_release_builds>.
OS: Windows 10 64 bit Build 19043.1348, Traditional Chinese I have same issue but since Libreoffice 7.2.0: Libreoffice 7.2.0 on Windows 10 - Works not good, slow typing Libreoffice 7.2.4 on Windows 10 - Works not good, slow typing I downgrade to Libreoffice 7.1.*: Libreoffice 7.1.4 on Windows 10 - Works perfectly Libreoffice 7.1.5 on Windows 10 - Works perfectly Libreoffice 7.1.6 on Windows 10 - Works perfectly Libreoffice 7.1.7 on Windows 10 - Works perfectly Libreoffice 7.1.8 on Windows 10 - Works perfectly
@Buovjaga Already having a VM achine with Windows 11? https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/ (In reply to Luboš Luňák from comment #12) > I don't have Windows 11. Could you give me a CPU profile from the Diagnostic > Tools in Visual Studio to possibly point to where the code is slow? My machine doesn't run that smooth
(In reply to Telesto from comment #17) > @Buovjaga > Already having a VM achine with Windows 11? > https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/ I'm still on Win 10 and I haven't done a dev setup on it up to now. Note for whoever tries with an own build: you need to use --enable-symbols and not --enable-dbgutil or --enable-debug because the debug functionality messes with performance.
*** Bug 146878 has been marked as a duplicate of this bug. ***
*** Bug 145575 has been marked as a duplicate of this bug. ***
*** Bug 147261 has been marked as a duplicate of this bug. ***
I'm also experiencing this issue on Windows 11. I think it's worth pointing out that spaces and some special characters type at normal speed. For example, periods, commas, exclamation points, semi-colons, colons, and quotation marks all type fast. However this is not true for all special characters. For example, brackets are slow. What's interesting is that whenever you type a character that "types fast" such as Space, all the letters you typed earlier which haven't displayed yet instantly appear. I'm not the only person to experience this behavior, see the comment here: https://www.reddit.com/r/libreoffice/comments/srymej/libreoffice_writer_input_lag_in_windows_11/hwypi61/
Now i have tested (again) the new 7.3 and the 7.3.1.1 beta, same problem. I have tested the special keys like Tim Perkin said. Here also the same. ,,,,,,,,,,, or dot ... typing fast the normal letters not. So test with aaaaaaaaa it's very very slow. I really don't understand why this problem is still not solved. I already reported this almost 3 months ago. The problem occurs on ALL new computers running Windows 11. Not just a few computers, but ALL the new computers or laptops. Several new versions have been released in the meantime, but each time the problem is still there. Even in the latest beta version, the problem is still there. The problem has already been reported by many people, already several bug reports are a copy of this one.
This issue affects Windows 10 x64 as well: Version: 7.2.5.2 (x64) / LibreOffice Community Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded Kindly expedite the assignment and fixing of this bug
(In reply to nareshsukhija from comment #24) > This issue affects Windows 10 x64 as well: > > Version: 7.2.5.2 (x64) / LibreOffice Community > Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5 > CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: > win > Locale: en-IN (en_IN); UI: en-US > Calc: threaded > > Kindly expedite the assignment and fixing of this bug Try deactivating Tools - Options - LibreOffice - View - Use Skia for all rendering
I tried deactivating Tools - Options - LibreOffice - View - Use Skia for all rendering, but did not notice any change. But activating it again seemed to work on my system. I noticed much improvement in selecting bits of text in a large document.
Try deactivating Tools - Options - LibreOffice - View - Use Skia for all rendering -> That's just the same. Even after activation back. (i have done this test before also).
I also tried "Use Skia for all rendering" but it did not help at all.
(In reply to nareshsukhija from comment #28) > I also tried "Use Skia for all rendering" but it did not help at all. Do you mean you tried *deactivating it* like I asked you to do?
Skia is irrelevant here. It appears to be a change in one Win32 API calls.
(In reply to Buovjaga from comment #29) > (In reply to nareshsukhija from comment #28) > > I also tried "Use Skia for all rendering" but it did not help at all. > > Do you mean you tried *deactivating it* like I asked you to do? Yes, this is what I had tried: "Try deactivating Tools - Options - LibreOffice - View - Use Skia for all rendering" It did not help fix the issue.
yes also tried with: Use Skia for all rendering: enabled or disabled -> same problem Use Skia for all software rendering: enabled or disabled -> same problem It's not a skia problem.
Luboš Luňák committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/17b39d150fce188f653632a3467891157375a1c6 fix Writer key event delayed compression (tdf#145963) It will be available in 7.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Luboš Luňák from comment #30) > Skia is irrelevant here. It appears to be a change in one Win32 API calls. Yep, nareshsukhija was using Win 10, though, so that is why I suspected their problem was different. nareshsukhija: tomorrow there will be a new build for Win-x86_64@tb77-TDF in https://dev-builds.libreoffice.org/daily/master/current.html which includes the fix for the Win 11 problem. Please test it. If the problem does not go away, open a new report.
I've installed the latest daily version, and I'm still experiencing the same issue.
(In reply to Tim Perkin from comment #35) > I've installed the latest daily version, and I'm still experiencing the same > issue. Unfortunately there is an issue with the Win-x86_64@tb77-TDF builder and the latest build is still 2022-02-18 04:04:32. So I was too optimistic in my earlier promise. Somebody needs to kick the build box and get it working.
(In reply to Tim Perkin from comment #35) > I've installed the latest daily version, and I'm still experiencing the same > issue. Please, share the info from Help - About LibreOffice
Luboš Luňák committed a patch related to this issue. It has been pushed to "libreoffice-7-3": https://git.libreoffice.org/core/commit/cb040adc86fa237c17d8800c9bda4757de230ebf fix Writer key event delayed compression (tdf#145963) It will be available in 7.3.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Luboš Luňák committed a patch related to this issue. It has been pushed to "libreoffice-7-2": https://git.libreoffice.org/core/commit/455a69825ab6cfd9595c4c763181cc797c859816 fix Writer key event delayed compression (tdf#145963) It will be available in 7.2.7. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Now there is a new build for Win-x86_64@tb77-TDF in https://dev-builds.libreoffice.org/daily/master/current.html
(In reply to Buovjaga from comment #40) > Now there is a new build for Win-x86_64@tb77-TDF in > https://dev-builds.libreoffice.org/daily/master/current.html @Telesto, Could you please give it a try ?
(In reply to Xisco Faulí from comment #41) > (In reply to Buovjaga from comment #40) > > Now there is a new build for Win-x86_64@tb77-TDF in > > https://dev-builds.libreoffice.org/daily/master/current.html > > @Telesto, Could you please give it a try ? It's surely improved a lot. I'm however unable to tell if it's native speed. Running Windows 11 on a VM with old hardware is far from optimal to give a definitive answer. Everything is laggy in general.
It works perfect with the new alpha 7.4. I have tested on a new computer with Windows 11. Typing in writer is working fine.
Luboš Luňák committed a patch related to this issue. It has been pushed to "libreoffice-7-3-1": https://git.libreoffice.org/core/commit/a2da9348e705181abba0068081b014d398f2bf3d fix Writer key event delayed compression (tdf#145963) It will be available in 7.3.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Unfotrtunately, I won't be able to try the new versions because I don't rights to do so on that device with Windows 10.
Luboš Luňák committed a patch related to this issue. It has been pushed to "libreoffice-7-2-6": https://git.libreoffice.org/core/commit/2cfd6762156852d86051b9b048da93f0aac266ff fix Writer key event delayed compression (tdf#145963) It will be available in 7.2.6. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Just had a chance to try this out. Works great for me. Thank you! Version: 7.3.2.0.0+ (x64) / LibreOffice Community Build ID: 7d64ec7d342da64e050ed9ac326b1af33d5c6955 CPU threads: 16; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Please note that with version 7.3.0.3, the issue is observed to be fixed on the device I had issues earlier with version 7.2.5.2.
Version: 7.2.6.2 (x64) / LibreOffice Community Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: zh-TW (zh_TW); UI: zh-TW Calc: threaded This issue has been fixed. Thank you.
(In reply to Dragon Chuang from comment #49) > Version: 7.2.6.2 (x64) / LibreOffice Community > Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 > CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: default; VCL: win > Locale: zh-TW (zh_TW); UI: zh-TW > Calc: threaded > > This issue has been fixed. Thank you. Thanks for checking. Setting to VERIFIED
It seems that the slow typing issue on windows 11 is indeed fixed. Thank you very much