1. I edit the document (one window). 2. I create the second window of this document (menu Window-> New Window). 3. In the second window I edit the text. The cursor is not displayed correctly. Attached is a video editing the document. The video shows how the numbers are entered (1 2 3 4 5). The input cursor is in the wrong position. Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded
Created attachment 182807 [details] The video shows how the numbers are entered (1 2 3 4 5). The input cursor is in the wrong position. The video shows how the numbers are entered (1 2 3 4 5). The input cursor is in the wrong position.
I could not reproduce the bug. Can you share a sample file for testing?
I can not today. Tomorrow. The original document has been modified. Hope it doesn't get in the way. Best Regards!
Created attachment 182818 [details] Problem document (my_doc1.odt).
Comment on attachment 182818 [details] Problem document (my_doc1.odt). my_doc1.odt
[Automated Action] NeedInfo-To-Unconfirmed
Tested just a little, but I think (by past experiences) that the problem is with the images. Not reproducible with: Version: 7.2.7.2 (x64) / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: es-MX (es_ES); UI: en-US Calc: CL
(In reply to LeroyG from comment #7) > Not reproducible > reproducible sometimes It happened twice, while testing in a new document (for bug #151416). But I could not find the way to reproduce it.
I tested with the provided file and could not reproduce in: Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.4.1~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded I tried for some time and could not see the bug in the cursor position. I am on kf5. I also tested with gen.
Created attachment 182987 [details] Video, the situation repeated itself. The error reappeared. My actions. 1. For the opened document I create one more window. 2. Document windows are arranged in order (not widened to full screen). 3. Editing a paragraph. I expand one window to full screen. 4. Apply the paragraph style. After that, it crashes. The cursor jumps to the wrong place. 5. I enter characters. The insertion point corresponds to the previous cursor position. But the cursor is displayed incorrectly. 6. I restore the size of the window. The cursor is displayed correctly. I did not change the language setting, because I was afraid that I would not be able to repeat the situation after turning on the English language.
I still can't reproduce it. Maybe it's a Windows-only issue? Leroy also experienced the issue in win.
(In reply to Rafael Lima from comment #11) > I still can't reproduce it. > > Maybe it's a Windows-only issue? Leroy also experienced the issue in win. Hello! So far, I've only encountered this problem on one PC. The hardware of this computer is not new. But Win10 works. What to do ... We'll have to leave it as it is.
No one confirmed this bug until now, so let's keep the status as Unconfirmed.
(In reply to Frants from comment #10) > Created attachment 182987 [details] > Video, the situation repeated itself. > > The error reappeared. > My actions. > 1. For the opened document I create one more window. > 2. Document windows are arranged in order (not widened to full screen). > 3. Editing a paragraph. I expand one window to full screen. > 4. Apply the paragraph style. After that, it crashes. The cursor jumps to > the wrong place. I could not reproduce it with your example file and the steps. Do you reproduce it with an unstable build (which installs separately)? Win-x86_64@tb77-TDF from https://dev-builds.libreoffice.org/daily/master/current.html Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5cd9de202765e243e41416802f3e4486b8a96f16 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded Version: 7.4.5.0.0+ (x64) / LibreOffice Community Build ID: 610880abd9f3be00451db51f05b7f4772c389b7a CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded
Dear Frants, 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 Frants, 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