@ve3oat :May be I do not understand your comment - but
Save saves into the current file location and all previous stuff (neglecting the track changes thing and of course all these forensic data recovery technologies) gets lost. It is overwriting the file with current document content. It doesn’t save into a copy - that’s my understanding of
Save , since using software and that’s why there is a
Save a copy functionality in
File menu of LibreOffice to address this issue and to mitigate those accidental faults like
CTRL+A followed by
CTRL+X and then
@ve3oat :May be I do not understand your comment - but
@anon73440385 : No, I think you understood correctly and you have explained very well what I was wondering about. I have never used Save a copy and didn’t realize the difference. Thanks for your explanation.
Libre Office has never behaved like this before but I’ve never used it before for such a large document. It sounds like it doesn’t behave like WORD. I just assumed I could use save and it would save. If so, what are the benefits for using Libre Office? Why would I want to use LO in lieu of WORD if save doesn’t work? Why isn’t there any recover function for this defect?
It is your decision what you want to use and the same thing could happen with any application and hence it is your habit you should revise and not the application.
I’ve been using WORD for over 20 yrs and have never had this problem before. And I’ve written many lengthy research papers, so my habits are irrelevant here. Don’t get defensive. Please answer my legitimate question. What are the benefits of using Libre Office over WORD? If I can’t rely on save and I have to rename each version why is that better (especially when you’re writing documents 25-500 pgs in length)? If there’s a benefit to the different tecnical approaches it would be good to know.
Clearly, something is not working as it should. Have you tried backing up all your documents, uninstalling LibreOffice and then re-installing it (perhaps a newer version)?
Also, saving separate versions of your documents, as suggested by @anon73440385, is excellent, and might provide some clue as to the underlying fault with the Save process.
@Adamf1 - Congratulations for driving without any seat belt for 20 years without an accident. Buy the car which drove you securely through the world of document creation for such long time without a backup strategy. And my admiration for still not seeing the benefit of having more than a single copy of your so important document in the light of you current problem and for your tenacity to refuse well-intentioned advice. Good luck …
Have you tried to see if you inadvertantly saved your document in a somewhat unexpected location? Have you tried the file search utility? (it was once named Sherlock on MacOS)
Since you seem to be a Word fan, have you saved your document as .doc(x) instead of .odt? In this case, you’re adding instabilities: the input-output filters do not guarantee exact conversions from one format to the other; moreover after some number of edits, the underlying XML is completely cluttered with conversion approximations making the document more exposed to formatting errors.
For me, I value Libreoffice because it does not spy on users. Microsoft Office products (including word) are geared toward cloud usage and collect telemetry data, so the concern at least for me was around privacy.
Loss of data can happen the same way with Word. Ideally use the “Save As” function for saving at particular milestones. Yes, you may end up with 100 copies of the document but it is a small inconvience to pay in exchange of losing all your work. Depending on the document I may save a new revision daily, or every couple of hours. It really depends on how much work you can afford to lose between Save As new files. Don’t know how many times versioning / multiple files has saved my ass. It is strongly recommended you save each milestone or major development as a file with a different name, eg timestamp.
Try select all (ctrl+a) and copy and paste into a basic text application such as writer.exe or notepad. Even if you cannot see any text or objects. Try copy and paste into notepad or write.exe.
Try restoring the file from the backup location: c:\users<USERNAME>\AppData\Roaming\LibreOffice\4\user\backup. It may be worth reading the full instructions.
Am hoping macOS file history works for you: View and restore past versions of documents on Mac - Apple Support
Be sure to make one or more copies before trying to recover the file in-situ.
Try to restore file using - windows File Versions/File History / Volume Shadow Copy
There are some tools out there for recovering data from macOS filesystems. (HFS+?) I have used GetDataBack for NTFS by runtime in the past and works a treat to recover complete files and open them straight up again. However, files are not always recovered in their entirety and potentially only fragments of the file may be recovered, but this may still be more desireable than having to start from scratch. Should only partially recovered fragment be recovered, you can then try using the strings command to extract strings from the file. (see below). There are plenty of data recovery / forensic tools out there so if GetDataBack doesn’t work you might try others.
You might also try Scalpel for linux/unix for linux/unix systems:
One would expect a large file to be greater than 5MB so if the size of file is less than say 5MB, then there may be salvageable data in the file which you can extract manually in order to help you rebuild/ copy or paste into a new document. Assuming the file was not password protected, you can use the unix/linux tool called strings. Apparently this is available on OSX, you need to run it under the console/command prompt. If it is not available you might try installing cygwin or installing a linux/unix in a virtual machine using Virtualbox or some other virtualisation software and run a copy of the file through string.
NB: if this does not yield reasonable results, you might first try extracting the contents of the file as if it is a zip type file. Try installing 7-zip then extract the contents of a copy of the file to an empty folder, run strings * >>all_text.txt, then open all_text.txt with a notepad or LibreOffice.
- You might try visiting the Computer Science department. Depending on whether you get someone who is compassionate enough to donate their time to help you retrieve your work. There are plenty of data recovery / forensic tools out there, just need to work out which ones will be useful.
Best of luck.
If this answer helped you, please accept it by clicking the check mark to the left and, karma permitting, upvote it. That will help other people with the same question.
In case you need clarification, edit your question (not an answer) or comment the relevant answer.
Thank you to those of you who provided constructive feedback and solutions. I think I’ve discovered a mystery flaw in the Libre Office software because when it happened the first time I thought it was something I did wrong, so I was meticulous in following certain saving procedures the 2nd time around. I even contacted a friend of mine from the Dept of Defense, who is skilled in finding missing documents and she couldn’t recover it. She also uses Libre Office and I told her what I did and she said it should’ve worked. I had her stumped and this woman is hired by the government to find things. She suggested switching over to Google docs. I use it for research collaborations but think that’s the most prudent option since I can’t afford to waste any more precious time on this research paper. There seems to be too many bugs in Libre Office based on all the ask.libreoffice questions I see in this forum.
There aren’t that much bugs in LO. At least 90% of the reported problems are user mishandling of the suite, mainly because they don’t take time to read the srtict minimum doc and don’t even use the built-in help. The biggest misunderstanding is that suites are not identical. When you switch from nails to screws, do you drive the screws with a hammer?
Computer programs are dumb. If some of your edits disappeared, you unfortunately saved your doc (at periodic intervals apparently) in this state. As long as you don’t close the application, undo history can save your life. But once closed, the saved file is the reference.
Concerning the number of bugs, I consider a sign of vitality they are reported. Contrary to M$ Office, we may hope the user-reported bug (as opposed to internal dev-reported ones) will be solved without depending on the good will of some commercial company. LO is quite stable and reliable.
Users are not bug counters, and can be dumb too, or just not used to this sort of thing, and I am smart enough to never use Google docs, or Microsoft Office, or anything those data leeches make, EVER, and am using FOSS for good reasons! Also: Making the user jump through hoops to “protect” their data from things that should never happen, fill their drives with bloat and use unwieldy procedures… just drives them away, and all that can be made to be handled internally, as some of my programs do have functioning undo after closing the doc and even the app! It’s called non destructive editing!
Oh, and I have encountered and reported plenty of bugs in Libreoffice over the last decade, none this bad!
Anyhoo, this is a help forum, not a bash the unsuspecting user forum, so thanks for the suggestions, but not the bashing!
blashrkh’s is, in my opinion, a particularly helpful response to the question (although it was not my question!). I lost portions of a document while applying attributes to a series of tables located there. There was nothing in the “undo” list that worked or applied to this document that would restore the section that had disappeared while I was looking at table attributes. The attention is a limited resource! What SAVED me was this advice: to try pasting into the Notepad just to see what was there. Et voila! The missing section must have been inadvertently “cut” (thank god, not “deleted”) and I got my data back from the Clipboard. Inadvertent things happen a lot. I’m very sympathetic to the post-writer here who lost all that work. I have experienced the same, and it wasn’t with LO in particular.
Writer offers a rudimentary version control feature.
When your document has already been saved once,
Versions becomes enabled.
If you want to backup several snapshots of your work, do
Versions and use the
Save New Version instead of the usual
Save command. With the version specific command, you are prompted for a comment to attach to each version.
The history of your document is displayed with time of backup, author and comment.
These versions are saved amid the document, i.e. they are carried over if you move the file across your computer. The drawback is that the file is larger than strictly necessary but you can step back if you are not satisfied with the current version.
However, ther is a really big inconvenience for me (this is why I call it a rudimentary feature). If you decide to step back to some earlier version, I highly advise you to make a copy of the original file before the step back.
From the history, you can select any previous version, but there are in a linear relationship, not in a tree-like hierarchy. The restored version becomes the current one and all ulterior versions are deleted. In case you finally decide that it was not pertinent to step back, you can’t revert to your most recent version! Thus the advice for a backup before definitive action.
To show the community your question has been answered, click the ✓ next to the correct answer, and “upvote” by clicking on the ^ arrow of any helpful answers. These are the mechanisms for communicating the quality of the Q&A on this site. Thanks!
In case you need clarification, edit your question (not an answer) or comment the relevant answer.
Thanks for the effort, but since file recovery (General/forensic) was covered above, and you didn’t point out that the tutorial you linked to was LO specific, I thought you meant forensic file recovery, and didn’t read it: Been there done that, and it was a big waste of time, as file recovery software cannot recover files from SSD’s, which are in wider use now than Disc drives.
I did figured it out myself though (I remember some things sometimes, just not everything all the time, nor when I need it most). (<:
The developers should work on making Writer (all programs) keep undo between sessions, and save backups transparently, only to be turned off in the settings, and that with a big red warning not to! I would really appreciate that, and thank them for all their efforts in making USER friendly apps keeping user convenience and productivity in mind.; After all, programs are there to be used, often for business and vital information, and not constantly tinkered with, that’s what developers do, not users.
Open LO, not Writer, Impress… > Recent Files> open any files with that name to find the right version, do a Save As, add a “Good” or something to the name and that should do it; Worked for me.
Now I also found out why my drive space is dwindling and will clean out everything in there I have archived and don’t need anymore, as well as find out how I can make LO delete them automatically, if there is a way to tell it when a doc is done and won’t be edited anymore (feature request!).
I guess I’m not a dumbass after all!
a way to tell it when a doc is done and won’t be edited anymore
LO is intended to create documents. Not using them any more is a user decision and LO has nothing to do with it (and even must not interfere with user decisions). Use the OS file browser to delete your old outdated documents. Note that this will not remove them from the recent files list. The recent files list is just some log that LO internally maintains but this does not mean at all that the listed files still exist. They may have been removed unbeknownst to LO (e.g. in the file browser).
must not interfere with user decisions
If the user tells the program that a document needs no further editing, as in my case with work orders, invoices, receipts… Which if I change once handed to the client may be fraudulent, then it is obviously my decision, and LO is not interfering (that would only be the case if I didn’t tell it to), and losing my data as appeared to have done IS interfering, and could have caused more trouble than it did. I save the docs as .pdf’s of course, and destroy the .odt’s, that way in any case of legal dispute, or audit… it not only shows I wasn’t fraudulent, but also shows I have no intent to defraud anyone or fix the books, by removing my ability to do so.
LO has everything to do with anything it does and can do for it’s users, so it would be a feature. It is an Office suite after all, right? I know how to use a file browser, and already did it, and thanks for pointing out that it lists non existent files: NOT GOOD!
I’d say that you have to implement a workflow where LO is only a step. Trying to use LO as the only tool for your job is faulty IMHO. You don’t use LO to email your documents, do you? (though LO can do it in a limited way) I prefer to use an ad-hoc tool at each step than a monster one-size-fits-all program. Such a monster would be terribly unstable and very hard to modify to keep up-to-date with evolving requirements. But YMMV.