Description: No matter how many times I hit save, if I shut my system down with libreoffice open, when I open it again, it reports "recover document". Steps to Reproduce: 1. Open document. 2. Save if required. 3. Restart system. Actual Results: When system comes up again, restart libreoffice, it asks you if you want to "recover the document". Expected Results: NO recovery if I have properly saved the document. Reproducible: Always User Profile Reset: No Additional Info: Its annoying because it creates doubt as to if the document is actually up to date with previous editing. I note that libreoffice does autosave a lot, even if the file is not modified. Perhaps the code to detect if office has modified the doc or not is not working?
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile ?
1. went into safe mode. 2. Opened a document. 3. Tried to exit program (having done nothing at all). 4. It reports "exit with modified document?". I did other experiments. First, it is autosaving regardless of if I actually changed the document. And just as in the safe mode above, I will close the document and get the "exit modified" complaint. Coming back up with libreoffice saying "recover document" happens if I shut down the system and don't first close libreoffice. If I go to it, save the doc, then exit libreoffice before shutting down, then it comes back up without the "recover document". Conclusion: libreoffice does not seem to know when I have not modified the document, or is automatically modifying itself in a way I don't know about (updating the time or something?). It does not seem fatal, I haven't noticed any document damage. Its just disconcerting to see libreoffice state that my document needs recovery, or that it thinks I modified the document when I did nothing. I would expect that libreoffice would not complain about loss of data, or state the document needs recovering if I didn't modify it. I like libreoffice, coming from Microsoft word. Regards, Scott Franco
[Automated Action] NeedInfo-To-Unconfirmed
Was this going to be followed up, or is it dead?
Since you used safe mode, I don't have more questions but just re reading all this, I think it's quite weird to shutdown a system without properly close all the applications. IMHO it's not a bug but I'll let other people judge. I can't help here so uncc myself.
I disagree, and I think you have mischaracterized the bug in any case. First of all, the user has a reasonable expectation that the file being edited will not be modified if the user has not modified it! I would expect to be able to open a file, not touch anything, just read it, and not have the program tell me that it has been modified. Having it autosave, say "exit with modifications" or whatever, tends to tell me it was modified by accident and thus something is wrong. Second, every other editor or program seems to be able to hook the shutdown notification and ask the user if they want to save or exit the document. I don't understand why, and I believe nobody can understand why libreoffice can't live by the same rules as other editors. Saying "I think it's quite weird to shutdown a system without properly close all the applications." makes it sound like a caused the error. I did no such thing.
Created attachment 183450 [details] libreoffice self-modifying bug screenshot
See attached screen shot. This is my file in libreoffice. It was opened, I didn't touch ANYTHING in the document, then tried to close it, then got that message. It says "your changes will be lost if you don't save them". I DIDN'T MAKE **** ANY **** changes at all! I just opened the file, left it for a minute or two, then tried to close libreoffice! ITS A BUG!
(In reply to Scott franco from comment #8) > See attached screen shot. > > This is my file in libreoffice. It was opened, I didn't touch ANYTHING in > the document, then tried to close it, then got that message. It says > "your changes will be lost if you don't save them". I DIDN'T MAKE **** ANY > **** > changes at all! I just opened the file, left it for a minute or two, then > tried to close libreoffice! > > ITS A BUG! Does it happen also with blank files or only this document or some specific group of documents? If it's tied to specific documents, would be good to have an example. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Dear Scott franco, 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 Scott franco, 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