Description: Even though Auto-Recovery of Writer-documents is switched on, sometimes it does not work! If one relies on that feature, and a crash happens, one can loose hours of work! Steps to Reproduce: I can see no pattern to reproduce this bug. Most of the time Auto-Recovery works fine. But on rare occasions it does not work. Actual Results: Auto-recovery did not work at all during several hours of working in Writer Expected Results: In case of a system crash my work should be easily recovered with the data that Auto-recovery has saved Reproducible: Sometimes User Profile Reset: No Additional Info: As this function is fundamental to safely handling work on documents, it needs to be totally reliable. Or at least, Writer should warn the user to save manually if the last time auto-recovery has successfully worked, exceeds a certain amount of time. So, my proposal would be a separate, independent control function, that checks the correct execution of auto-recovery. That way, even if auto-recovery does stop working for some reason, the user will be warned & can save the file manually & will therefore not loose hours of work if a crash should occur. Version: 6.4.7.2 Build-ID: 1:6.4.7-0ubuntu0.20.04.1 CPU-Threads: 2; BS: Linux 5.4; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-CH (de_CH.UTF-8); UI-Sprache: de-DE Calc: threaded
Thank you for reporting the bug. 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. Change to RESOLVED WORKSFORME, if the problem went away.
Dear ATI, 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 ATI, 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