There is nothing to recover, and this bug doesn't allow to start the app. Even pressing cancel in the recovery dialog doesn't help at all... Uninstall-reinstall doesn't help.
Recent trial to start: "Due to an unexpected error, LibreOffice crashed." --> Recovery dialog opens -> OK -> That's all (The whole package was reinstalled several times, no stability issues otherwise...)
You can try 2 things: 1) Start a version of OOo (I use Go-oo). Quit. Run LO again. Don't ask me why, but it sometimes works. 2) Rename your user account in 'application data/libreoffice' -> hidden directory. Start LO again.
(In reply to comment #2) > You can try 2 things: > > 1) Start a version of OOo (I use Go-oo). Quit. Run LO again. Don't ask me why, > but it sometimes works. > 2) Rename your user account in 'application data/libreoffice' -> hidden > directory. Start LO again. Tried #2. Removed the Application Data/LibreOffice folder. Everything works fine. Shall I close this bug, or would you like to let it open? (It seems that after installing 3.4.2 something went wrong, and left an unusable config folder left.)
It just happend to me and I used solution #1 to fix it ;) You can close this report, because it's not a real bug. Sometimes something is off on windows. That's a M$ problem.
See comment 4: "That's a M$ problem."
mail@tamas-nagy.net, were you offended by xdmx's comment, and marked this bug as resolved because of that? Please note that none of the actual LibreOffice developers that I know is in the habit of using derogatory terms like "M$"... that is so last century. We value our Windows-based users as much as our users on other platforms.
Reopening, bug reporter thought comment #4 was an "official" LibreOffice maintainer response.
(In reply to comment #6) > mail@tamas-nagy.net, were you offended by xdmx's comment, and marked this bug > as resolved because of that? Please note that none of the actual LibreOffice > developers that I know is in the habit of using derogatory terms like "M$"... > that is so last century. We value our Windows-based users as much as our users > on other platforms. Sorry, but I didn't try to offend anyone. I use windows myself (private & at work). So I *know* that sometimes things go wrong, sometimes with this program, sometimes with that program. I wasn't talking specific with LO in mind. But, I happen to have this problem too [sometimes]. When I commented the last time I *just* fixed the problem myself. So I know what i'm talking about. If the problem for the reported is fixed too, then the report could be closed.
Closing, see comment 3. It must have been a temporary problem, maybe a corrupted user profile or somesuch.