Issue 101366 - AutoRecover did not recover document
Summary: AutoRecover did not recover document
Status: CLOSED DUPLICATE of issue 92968
Alias: None
Product: Impress
Classification: Application
Component: save-export (show other issues)
Version: OOo 3.0
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: graphicsneedsconfirm
QA Contact: issues@graphics
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2009-04-27 11:29 UTC by froh
Modified: 2009-07-12 18:11 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description froh 2009-04-27 11:29:03 UTC
I was working on a presentation and every now and then I saw the autosave
progress bar.

Then OOo crashed and informed me that it would auto recover the documents I had
been working on.

The auto recovery however only brought me the very initial version of the
document back.

This is the what I now find in the autosave directory:

0 froh@byron:/space/SVN/Driver-Process/trunk/doc $ l ~/.ooo3/user/backup/
total 392
drwxr-xr-x  2 froh users   4096 Apr 27 12:11 ./
drwxr-xr-x 17 froh users   4096 Oct 24  2008 ../
-rw-r--r--  1 froh users     79 Apr 27 11:55 .~lock.Driver Build.odp_1.odp#
-rw-------  1 froh users      0 Apr 27 11:55 Driver Build.odp_1.odp
-rw-------  1 froh users      0 Apr 27 11:55 Driver Build.odp_10.odp
-rw-------  1 froh users 293129 Apr 27 12:11 Driver Build.odp_2.odp
-rw-------  1 froh users  37860 Apr 27 12:10 PLDP II Design document.odt_0.odt
-rw-------  1 froh users  48522 Apr 27 12:10 prd_pldp_2_20090424.odt_0.odt

I've lost 2h of very focused and concentrated work and I'm dead annoyed.

I have the fantasy that the crash tried to do a last auto save, which then was
empty.

either this overrode the last correct auto save or the auto recover did not
handle this appropriately.

In any case it seems to me that auto save and recover are not transactional.

This is on openSUSE 11.1 on x86, using OOO300m21 (Build: 9319)  aka Build 3.0.0.9
Comment 1 wolframgarten 2009-04-27 11:40:57 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.
Comment 2 froh 2009-04-28 09:04:48 UTC
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?
Comment 3 mmeeks 2009-04-28 09:47:23 UTC
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 ***
Comment 4 Mechtilde 2009-07-12 18:11:48 UTC
duplicate -> closed