Issue 111290 - Better protection for file if crash occurs
Summary: Better protection for file if crash occurs
Status: CLOSED DUPLICATE of issue 126869
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 3.2
Hardware: Unknown All
: P3 Trivial with 11 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL: http://user.services.openoffice.org/e...
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-30 14:14 UTC by oooforum (fr)
Modified: 2017-05-20 10:01 UTC (History)
5 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description oooforum (fr) 2010-04-30 14:14:15 UTC 
Hello,
If a crash occurs, it often happens that OOO can't recover the file. The file is
damaged: zip is corrupted and/or content.xml size is 0.
Why OOo don't work on a copy? 
The steps would be:
- user open a ODF document
- OOo rename .od* in .tmp and copy .tmp in .od*
- if user save the document
- OOo delete .tmp, rename .*od* in .tmp and copy .tmp in .od*
- if user close the document
- OOo delete .tmp
This could prevent the problem (see URL above). If a system error occurs, power
ends or crash OOo and corrupt the .od*, user can recover the previous version to
rename .tmp in .od*.
This could improve security cause many users forgot to check "Always create
backup copy" option.
Comment 1 touchzell 2010-06-29 17:16:23 UTC 
*** Issue 111290 has been confirmed by votes. ***
Comment 2 richard_g 2011-12-01 14:11:32 UTC 
Hello,

In addition of making OOo to work on a copy, the security could be easily enhanced by SETTING THE "Always create backup copy" OPTION BY DEFAULT! Beginners don't know this option and always come on the OOoforum after a crash when it is too late!
Comment 3 Hagar Delest 2012-09-14 20:35:39 UTC 
For the record:
https://issues.apache.org/ooo/show_bug.cgi?id=107847
Comment 4 orcmid 2016-03-12 20:22:54 UTC 
This is being marked as a duplicate of Issue 126869 for the purposes of collecting all defects of this kind under a single umbrella for analysis.  (Confirming by votes is peculiar but there is no doubt that this problem exists.)

Here, resolution does not mean there is a conclusion, merely that we are combining issues.

*** This issue has been marked as a duplicate of issue 126869 ***
Comment 5 orcmid 2016-03-12 20:23:49 UTC 
Changed from Feature to Defect, although a proposed fix was made here.