Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi,

I am regularly getting a dialog box stating that one of the LibreOffice Documents I am working on needs to be recovered.

This happens despite...
1. The document actually saving and libreoffice closing without any errors.
2. Quite regularly -- 5-10 times a day.

I have searched around and only found one error log that has libreoffice mentioned. This is hs_err_pid####.log found in my HOME directory.

I have provided a link to one of the many log below for interest. I note however that the logs do not appear when the dialog box appears, or should I say prior to the dialog appearing. So...

1. Can someone explain what normally triggers this 'recover a file' dialog to appear (system events or file specific events)? 2. Where in the system is the cause of the 'error' stored (e.g. log, event log, etc)?
3. What does the error log linked[1] to signify?

[1] http://www.botanicusaustralia.com.au/Documents/LOJavaErr.log

I am using Ubuntu 10.04 LTR, LibreOffice 3.3.0 [OOO330m19 (Build:6)
tag libreoffice-3.3.0.4, Ubuntu package 1:3.3.0-1lucid1]

--
Cheers Simon

   Simon Cropper
   Principal Consultant
   Botanicus Australia Pty Ltd
   PO Box 160, Sunshine, VIC
   W: www.botanicusaustralia.com.au

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.