Description: several times the automatic save option of writer runs but it never save the files, if you do not save manually the document, it is lost... also the restoring of documents does not recovers anything Steps to Reproduce: 1.open any file 2.make any change 3.wait the automatic save function, even if it run, the new changes will not be saved Actual Results: not automatic save functioning Expected Results: lost information if you do not save manually Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: es Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
*** This bug has been marked as a duplicate of bug 152463 ***
If the autorecovery was active in Tools - Options - Load/Save - General and it was run, this is not a duplicate of bug 152463
(In reply to Buovjaga from comment #2) > If the autorecovery was active in Tools - Options - Load/Save - General and > it was run, this is not a duplicate of bug 152463 ksso, could you please check? => NEEDINFO
Hi, this is a video where its explained that in more than ten minures the automatic save option doesnt do nothing (the indicator is the red point on the save icon) Only when I click over the save icon, the red point disappear, indicating that the saving really happens, and that there is not danger if something happens and lost unsaved changes thanks https://www.youtube.com/watch?v=ain89d0GiaA
I have done this experiment with a new text with 500 pages just text: - Set like you 1 minute AutoRecovery and Backup - after 1 minute it's loading in the status bar, like it's saving, but status bar icon is still red (unsaved) and also in standard toolbar is still red (unsaved) - in a terminal I found the process ID for soffice and kill it - after opening LibreOffice, it offers to recover, and I get all my 500 pages, so, they were saved, but the symbol for saving are still red, even after recovery I can confirm just the red icons, but not the recovery process (everything fine in my case).
Dear ksso, 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 ksso, 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