- Did you already reboot your computer? If not, please do.
- Which documents does LibreOffice want to restore? Do you have a
path? If yes, please go to the given directory and see, if there is a
*.lck file, which has a similar name like the original file, that
LibreOffice wants to restore. You can safely delete this *.lck file.
- If you don't see such a file, please check your file manager and
see, if you can change it in such a way to show hidden files.
Once the *.lck file is deleted try to restart LibreOffice. It should
work now and start as normal.
> Pretty sure I've found a bug:
> Upon opening LIbreOffice, I get this error message:
> "Restore Windows
> The application “LibreOffice” unexpectedly quit while trying to restore
> its windows. Do you want to try to restore its windows again?"
> with two buttons:
> "Don't Restore Windows" "Restore Windows"
> Neither button works, the program crashes. Cannot view or create new
> documents, my entire word processing ability is at a standstill.
> If anyone can help, it would be much appreciated!
> Thank you,
It is indeed a nasty bug, but until now, it has not been solved.
In the mean time, you can use the following solution:
(quote from previous discussion)
> The problem is some conflict between Lion and LibO, and not even on all
> Macs with Lion. I have it from time to time on a MBP, not on my iMac.
> How to avoid it: closing LibO before shutting down your computer.
> It will still occur when LiboO hangs and you have to Force Quit.
> Remedy: use Terminal to throw away the savedState file that seems to cause
> the problem of the obstinate restore/don't restore window.
> Open Terminal (in your Applications/Programs folder > Auxiliaries or Help
> Programs) after the prompt ($) type:
> rm -fr ~/Library/Saved\ Application\ State/org.libreoffice.script.
> followed by a return and the problem should be solved...
> You can find the Terminal command solution in bug report 39007.
> https://bugs.freedesktop.org/show_bug.cgi?id=39007 > >
> It was discussed on this list a few months ago, but the bug still isn't
> solved in 3.4.4, probably causing quite a few Mac-users to abandon LibO!