http://www.shamusyoung.com/twentysidedtale/?p=11809 This is very bad for the Libreoffice reputation. Get details of crash from Shamus, if necessary. Make certain that document recovery never saves over the original document without the user saving it, and that the autosave directory isn't deleted on crash/recovery, or disable autosave until this bug is fixed. I'm terribly sorry for the lack of technical details of the crash.
NOT reproducible with "LibreOffice 3.4.0RC2 – WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:12)]". I provoked a crash due to "Bug 36820 - PDFEXPORT with option "Tagged PDF" crashes WRITER documents", Recovery worked perfect for me. Might be a DUP of "Bug 34805 - FILESAFE .doc files are not recoverable and hence not autosaved" or "Bug 32554 - document recovery behaves unpredictable", but who can know with contributed rare information? This is not a valid bug report, ANY useful information is missing. So -> invalid @Jason: It's too painful, I'm uncomfortable with reading the text you linked where you spread your incompetence for using a powerful text processor (BTW: The quick sly fox would use menu 'Format > Paragraph > Alignment > Justified - Last Line = Left', what is default for my WRITER), and a short reading does not expect any useful information. For your sermons Google Docs really might be the best choice for you. Please feel free to reopen this report if you believe that LibO might be useful for you and if you can contribute additional information due to <http://wiki.documentfoundation.org/BugReport> (especially BugReport Details)! You should please: - Write a meaningful Summary - Attach a sample document - Attach screenshots with comments (you can add information using LibO DRAW and then attach your screenshot with comments as PDF) if necessary - Contribute a step by step instruction containing every key press and every mouse click how to reproduce your problem - add information -- what exactly is unexpected -- and why do you believe it's unexpected -- concerning your PC -- concerning your OS -- concerning your LibO version and localization (UI language) –- Libo settings that might be related to your problems (video hardware acceleration ...) -- how you launch LibO -- everything else crossing your mind after you read a.m. URL Can you please file Bug reports with status UNCONFIRMED if your are not absolutely sure that you contributed all required background information and that the problem will be reproducible with information you can provide? Thank you!