Description: Libre Offie Writer Версия: 6.4.4.2 (x64) ID сборки: 3d775be2011f3886db32dfd395a6a6d1ca2630ff Потоков ЦП: 4; ОС: Windows 10.0 Build 18363; Отрисовка ИП: по умолчанию; VCL: win; Локаль: ru-RU (ru_RU); Язык интерфейса: ru-RU Calc: CL I was simply replacing one selected character in text on a regular page of my .docx document when autosave occured just exactly the moment I entered a replacement character from keyboard. The next moment I found myself unable to type or undo or make any other correction because the autosave progress bar in status panel was restarting infinitely, saving and saving, until after 3 minutes I terminated all LibreOffice processes via Task Manager. As for what happened to my document. I lost all changes and 10 minutes of hard work, all the calculated values for my report. On next attempt to open the document it was found defective and restoration procedure started (oh, please, remove this useless feature) upon "successful" restoration not only the changes were lost, but the picture (plot) I inserted earlier overlaped with text, even thoug I made specific precautions setting parameters "обтекание" and "привязка" for which I do not know exact originals in EN version. Steps to Reproduce: 1. Set autosave time 2. Select a character in your .docx document 3. Type over selected character in the exact moment of autosave Actual Results: Does not save, infinite loop, loss of control over application Expected Results: I expected to continue editing Reproducible: Didn't try User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: ru Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: yes Версия: 6.4.4.2 (x64) ID сборки: 3d775be2011f3886db32dfd395a6a6d1ca2630ff Потоков ЦП: 4; ОС: Windows 10.0 Build 18363; Отрисовка ИП: по умолчанию; VCL: win; Локаль: ru-RU (ru_RU); Язык интерфейса: ru-RU Calc: CL
Went to Tools - Options - Load/Save - General. Changed autorecovery saving frequency to 1 minute. Used the dt, F3 autotext and copied and pasted many times to get a document with 3600 pages, saved. Pressed Insert key and started typing in overwrite mode for a couple of minutes. No infinite loop observed. Tried both with an ODT and a DOCX. Peter: are you able to reproduce the problem reliably? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away. Version: 7.1.0.0.alpha0+ (x64) Build ID: df74aef7159d7155addf78cfc4d139485945d794 CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: default; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded
Dear Peter Protsenco, 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 Peter Protsenco, 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