Bug 147261 - Sluggish typing in LibreOffice 7.2.5.2. (Writer) for Windows 11
Summary: Sluggish typing in LibreOffice 7.2.5.2. (Writer) for Windows 11
Status: RESOLVED DUPLICATE of bug 145963
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.5.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-07 16:54 UTC by Miquel Burgos
Modified: 2022-02-07 18:05 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miquel Burgos 2022-02-07 16:54:05 UTC
Description:
I have Windows 11 in my work computer, and I've realized that, since the last upgrade, word typing in Writer is sluggish: in general, the word I type is not displayed until I stop typing, which is quite painful, and many times some letter goes missing in the middle, also.

This did not happen in the previous version, nor does it happen in my home computer, where I have Ubuntu. I have seen people having similar problems and tried the solutions given to them, but none of them works for me (enabling/disabling Java, hardware acceleration, and so on).

Can you help? Thanks in advance.

Steps to Reproduce:
1. Just type some word longer than 2-3 characters.
2. Check the sluggishness in the process.
3. When you stop typing is when the word appears.

Actual Results:
The typing is sluggish.

Expected Results:
Characters should appear on the screen as soon as I type them on the keyboard.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.2.5.2 (x64) / LibreOffice Community
Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5
CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: default; VCL: win
Locale: ca-ES (ca_ES); UI: ca-ES
Calc: threaded
Comment 1 Aron Budea 2022-02-07 18:05:42 UTC
Looks like this is the same as bug 145963.

*** This bug has been marked as a duplicate of bug 145963 ***