Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | AutoRecover did not recover document | ||
---|---|---|---|
Product: | Impress | Reporter: | froh <susanne.oberhauser> |
Component: | save-export | Assignee: | graphicsneedsconfirm |
Status: | CLOSED DUPLICATE | QA Contact: | issues@graphics <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, mmeeks |
Version: | OOo 3.0 | Keywords: | needmoreinfo |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
froh
2009-04-27 11:29:03 UTC
I'm sad to hear that so much of your work was lost. But for production work I recommend to use one of the major releases and not one of the developer snapshots which your version (DEV300m21) seems to be. Is there any way to reproduce the problem? Otherwise there is not much we can do about it , sorry. I'm not sure whether AutoSave data loss should only be investigated if it can be reproduced :) ? Fact is, for me the autosave was not transactional, and somehow OOo decided to use a dated save (after reporting the bug I noticed that _some_ changes from the beginning of the session had survived the crash.) instead of the most recent one. Re: development snapshot I'd love to pull in Michael Meeks from Novell, but how do I do a user search in this bugzilla? Looks like you're a victim of this regression in 3.0:
> fix issue 92968 (autorecovery does not recover the previously
> auto-saved document version, but the last one which was
> regularly saved)
If you use 3.0.1 hopefully things will be better; really sorry about your
experience though - this was a shocking bug. Sadly we have no automated
regression testing to catch this either (that I'm aware of).
*** This issue has been marked as a duplicate of 92968 ***
duplicate -> closed |