Description: The bug can be recreated by editing a writer document with track changes on, once the auto save kicks in some of the corrected, deleted or inserted words disappears on the current pages whereas the alterations may still be visible on the other pages of the document . This leads to confusion about where changes has been made in the documents, saving and closing the documents restore all the corrections or simply using the undo and redo command can also restore the changes on the document Steps to Reproduce: 1. Open a writer document in .docx format (observed under the format several times) 2. Record and track changes leaving the changes visible 3. Wait for auto save to run Actual Results: The alteration, addition or deletion is likely to disappear Undo and redo to make alterations to appear again or close and reopen document Expected Results: Auto save should run its normal course without visible tracked changes not disappearing Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US 7.4.2-2 Calc: threaded
I can't reproduce in: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6e66b5d75b4cda0314b64f4d12ef9e4350751470 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded or: Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Could you please see if you can reproduce in safe mode? (Help > Restart in safe mode...)
Safe mode does not have autosave enabled by default, enabling it requires restart so the bug may not be reproducible in safe mode. Restarting the safe mode reverts back to the user settings, and restarting again in safe mode does not have autosave enabled. Note: Tried in safe mode but autosave did not kick in because libreoffice was not restarted
Thank you, Taofeek. A few more questions: - Could please try with a fresh user profile? (Making sure you are familiar with what might be lost, or backing it up beforehand.) https://wiki.documentfoundation.org/UserProfile - If the issue persists, could you test a recent master build as well? -> https://dev-builds.libreoffice.org/daily/master/current.html - Has the issue only happened with DOCX, and never with ODT? - A video of the issue could be useful too, if you are able to attach that.
Dear Taofeek, 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 Taofeek, 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