Issue 56518 - sxw document crashes OO.o 2.0 with unrecoverable error
Summary: sxw document crashes OO.o 2.0 with unrecoverable error
Status: CLOSED DUPLICATE of issue 46683
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 2.0
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: flr
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-24 08:47 UTC by avagula
Modified: 2013-08-07 14:42 UTC (History)
1 user (show)

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


Attachments
sample file (19.35 KB, application/vnd.sun.xml.writer)
2005-10-24 08:48 UTC, avagula
no flags Details
File repaired resaving with OOo1.1.4 (15.38 KB, application/vnd.sun.xml.writer)
2005-10-25 06:35 UTC, eric.savary
no flags Details
File resaved in OOo2.0 -> no problem anymore (16.00 KB, application/vnd.sun.xml.writer)
2005-10-25 06:37 UTC, eric.savary
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description avagula 2005-10-24 08:47:33 UTC
Attached file crashes OO.o. It is a 8-page sxw document with TOC. Document is
last time saved with the same version of OO.o (2.0).
Comment 1 avagula 2005-10-24 08:48:44 UTC
Created attachment 30762 [details]
sample file
Comment 2 michael.ruess 2005-10-24 08:57:25 UTC
Reassigned to ES.
Comment 3 eric.savary 2005-10-25 06:33:52 UTC
ES->FLR: please have a look. I could repair the file saving again with OOo
1.1.4. Saving again in OOo 2.0 (m132) I cannot recreate the problem.
Comment 4 eric.savary 2005-10-25 06:35:51 UTC
Created attachment 30792 [details]
File repaired resaving with OOo1.1.4
Comment 5 eric.savary 2005-10-25 06:37:10 UTC
Created attachment 30793 [details]
File resaved in OOo2.0 -> no problem anymore
Comment 6 avagula 2005-10-25 10:35:11 UTC
es: Thank you for file, I really needed it :)
so the bug seems to be, that OO.o 2.0 cannot recover what 1.1.4 can? 
And crashing, and corrupted file when saving to sxw?
What I did before the file got corrupted:
1. opened file
2. changed printing options (selected another printer)
3. printed document out, wanted to close file
4. after prompt saved file 
5. closed file and shutdown computer
Next time I logged in, file could not be opened.
Comment 7 avagula 2005-10-25 10:43:48 UTC
hm, when thinking twice - as corruption took place while saving at prompt, maybe
OO.o closed file 'too fast' and there was some writing error?
Excuse me when this sounds stupid. :)
It happened on Windows XP sp2 computer, without any antivirus software installed.
Comment 8 eric.savary 2005-10-27 15:40:16 UTC
duplicate fixed.

To repair your file:
- unzip the file
- load the contenxt.xml in a editor
- replace all _5f_5f_5f_5f_5f_5f_5f_5f_5f_5f_5f_5f_5f_5f_5f_5f_5f_5f_5f... to
get only one _5f.
- save
- rezip file

*** This issue has been marked as a duplicate of 46683 ***
Comment 9 eric.savary 2005-10-27 15:41:36 UTC
closed
Comment 10 eric.savary 2007-05-17 12:09:03 UTC
*** Issue 77456 has been marked as a duplicate of this issue. ***