My Recent Blogs
- Forward commands from PHP to LightwaveRF
- My Alexa skill is now live in the UK
- Chi Wai Kung Fu @ Cheltenham now with extra tech!
- How to remove duplicates in Amazon Music playlists
- Send messages to another room using Amazon #Alexa #dirtyhack
- How to call a webservice api from Amazon Alexa using Javascript in a Lambda function
- Amazon Alexa – what it needs to do next
- Holistic Software Development – the book
- Howto: Controlling LightwaveRF lights with a Raspberry Pi, Flirc and Logitech Harmony One IR remote
- Holistic Software Development @AgileInABag London 12 June 2015
Categories
Twitter feed
- RT @Werner: Processor Speculative Execution Research Disclosure - @awscloud disclosure wrt the processor vulnerability - "All but a small… 3 hours ago
- Hootenanny just spoiled World's Strongest Man! 3 days ago
- Not happy that @amazonmusic is cancelling uploaded music storage. I play lots of uploaded tracks that aren't in th… twitter.com/i/web/status/9… 2 weeks ago
- Neo-Nazis are trying to spread hatred through comedy. This isn’t funny. google.com/newsstand/s/CB… 2 weeks ago
- RT @ncsc: Secure development & deployment principles move to beta... ncsc.gov.uk/blog-post/secu… 2 weeks ago
agile
agile@scale
agile at scale
alexa
amazon
architecture
behavioural science
beta
blogging
build
business change
chrome
cognitive science
communication
delphi
design
development
essup
esswork
firefox
google
governance
holistic communication
hsd
hse
IBM
Jazz
kanban
kung fu
lazarus
leadership
lean
linguistics
linux
lols
management
MCIF
microsoft
portfolio management
process
process improvement
programming
psychology
Rational
release
requirements
review
RPM
RQM
RRC
rsdc2008
RTC
RUP
scm
screenshot
scrum
sketch
software
software-development
sp
systems thinking
tara
teaming
team_concert
testing
twitter
ubuntu
uml
use case
user story
vega
visual studio
web2.0
windows
wordpress
Archives
Blogroll
Copyright
© Mike MacDonagh 2004-2012
All rights reserved
All rights reserved

Thanks for this info!! I’ve hit a small problem though, when I was setting the file type, I said “odt” instead of “doc” as I save in Libre’s natural format. I then am presented with a list of commands. If I change back to “doc” then foremost has a good time reading my system and filling up the “recovered” folder as promised. Any idea how to add “odt” into the search requirements? I desperately need a certain document that decided to go from 5 pages to empty (0 bytes).
Sorry I was lucky in that I was writing stuff for windows users so I’d been saving in doc format. I did read something about people using other tools like “scalpel” with varying levels of success. Check out http://www.pc-freak.net/blog/recovering-deleted-files-on-ext3-filesystem-in-linux/ for some more detailed stuff on the other tools. Good luck!
Try using -t zip. The man page for foremost points out that OpenOffice documents are just zipped XML so this option will recover them (along with other stuff that you might not care about)
Thanks for this info, Mike. I thought I was being safe keeping a chapter I was writing on dropbox because of their 30 day time machine feature, then I got worried when 8 hours of writing later my entire chapter disappeared and I saw that all dropbox had in its history was the outline file I started with–all this despite frequent, obsessive saves that became second nature to me while writing my dissertation a few years ago. So much for the cloud, huh?
Worked like a charm. I would only add that I’m on Ubuntu and had to chown the directory to my username before I could open the recovered files even though I had created the file in my user’s directory. Thanks again.
@Cam, I don’t know if you’re still around. I use .doc as well, because it helps with collaboration–not because I like office. I read in foremost’s man page that the headers for .odt are the same as for .zip because they are just XML in a zip wrapper, so you should be able to get them that way. Good luck. Maybe this can help someone else. The zero byte thing is exactly what happened to my document.
Hi John, I’m glad this helped you out 🙂
thanks … helped me too … for me it was case of a xls file. Is there a patch out for this or shall i switch to some alternative of Libre office ?
Not that I’ve seen but it’s pretty easy to recreate so hopefully will be fixed soon
Anyone else annoyed that the blogger advertises libre office document recovery on linux, but it’s only valid if the document was saved as .doc? Welp that just wasted a couple of minutes that I’ll never get back.
It’s not an advert joe, it’s all free stuff. As mentioned in the other comments odt’s are just zips so you might still be able recover them.
after running foremost, and finishing, the /recovery/doc folder came out empty. the log in /recovery has recorded the files, named the way you said they would be named (ex. 1234567.doc) but there are nowhere to be found. using Lubuntu btw.
Sorry, I’ve got no experience of Lubuntu 😦
same problem on xubuntu
Pingback: LibreOffice Writer OLE problem - Page 2
I have the same problem but I’m running on a Mac Os W. What should I do ?
Um… Ask someone who knows about macs 😉
hi, i just lost my file that was on docx on libre office, when i try to recovers it says that does not exist. and it was in c://appdata.temporaryinternetfiles 😦 i am so sad!!
FYI to warn the author and others: the reason some word processor files are saved in .zip format is that it’s how they implement the Record/Track Changes function. Through experimenting, I learned in 2010 that .doc files for recent versions of Word are saved exactly the same way if the program is recording changes, so they can actually be corrupted just as easily.
My solution so far has been to use SpiderOak as my cloud sync/backup provider, as free accounts there keep separate copies of every single version of a file ever saved, and monitor my writing, auto-save & auto-backup folders. That way, if a file does become corrupt, I can easily just roll back to the version saved a few minutes earlier.
Thanks for the clarification. I tend to use a folder in Dropbox for the same reason.
Hi Folks! Stumbled on this site trying to find the answer to my quirky issue. Occasionally LibreOffice will save .odt documents which are reported now as 0 bytes. (!) Opening from Files menu is via gedit (OS = Ubuntu 16.04), which displays as a mess. Found if in the Files Menu I rename the file it immediately displayed the proper file size and can be opened my LibreOffice again. I’ve just been adding a ‘hyphen one’, so Barry.odt gets renamed to Barry-1.odt.
Problem has occurred on both the internal drive, USB drives, and thumbdrives.
Don’t know how helpful this will be but might be easier than some of the other recovery options.