Description: Examples: A. The shape of a mouse-dragged text highlight mismatches the shape of the displayed text, as if the text display and the highlight see different parts of the document (or text flow). Subsequent typing might then corrupt the text, losing lengths of text, without being able to undo. B. Cut-and-paste of a few words within the same document can likewise corrupt the display and the underlying text. Undo is sometimes possible. C. Typing into a paragraph sometimes causes the remainder of a chapter to disappear. Scrolling to the next page can sometimes make the text re-appear and disappear between display refreshes. Steps to Reproduce: Case A: 1. Select text in a Writer document. In my case, the document contained 68000 words. 2. Type to replace the text. Actual Results: Sometimes, the text highlight mismatches the shape of the displayed text, as if the text display and the highlight see different parts of the document (or text flow). This is a 'red flag' that subsequent typing might then corrupt the text, losing lengths of text, sometimes without being able to undo. Expected Results: The typed text replaces the highlighted text. Reproducible: Sometimes User Profile Reset: Yes Additional Info: I've listed three possibly-related issues in the Description. I'm attempting to create a reproducible or minimal case, as I haven't yet determined prerequisites to this bug occurring. 'Save As' (fresh document) does not fix it. Some notes: - 68,000-word document, using paragraph and character styling. - Display scaling 200%, no 'High DPI' overrides in Windows. - Multiple page view, zoomed to about 90% of the screen width. - Use hardware acceleration: off. - Removed any non-bundled extensions (Alternative Searching, Language Tool). - Safe mode test is not helpful in this case, because reproducibility is rare. I also occasionally see Bug 123456 (misaligned rendering zones) when placing my cursor in a paragraph. Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded
Tools -> Options - View -> Check Force Skia Software rendering press OK & restart
Thanks, @telesto, I'll see how that goes. I didn't have "Force Skia Software rendering" enabled when using v7.0.3.1. With this config, I have a laptop with Intel CPU, and (not enabled in this app) a mobile GTX. "Use hardware acceleration" is greyed out. v7.1 Beta looks a bit different there: "Use hardware acceleration" and "Force Skia software rendering" are both greyed out.
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.
Dear dev, 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
Dear dev, 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