Apache OpenOffice (AOO) Bugzilla – Issue 1424
Unrocoverable Application Crash while openning a SXW Documents.
Last modified: 2003-09-08 16:56:16 UTC
The OO627 run on Win2000 with all critical updates and JAVA 1.3.1. The Document crash the application unexpectedly in Version 627 and more elegantly on Version633. The document was taken from a Word 98 Document. Then Saved into the Writer 6.0 Format (as requested when closing the application). The document was easily editable in it's new format .SXW many revision of the document were done during that day (Open/Mod/Save/Close) without any problems. The last modification in the document was the import of two JPG Images and manipulation of the viewing size. When File was tried to be reopen both version 627 and 633 could perform the job. Even the Backup could not be used which may indicate that the problem was created earlier than the insertion of the two image file. As the document is an important one I will Look into the code for a recovery mechanism in theses case to gather the most data back as possible. Is it possible to attach both Backup and Latest File ? BG
Created attachment 440 [details] Latest Saved Document that crash Version 627 and 633
Created attachment 441 [details] Latest Backup Document that also crash with Version 627 and 633
An exception is thrown when SwXShape tries to set the property 'AnchorPageNo'. Internal bug id for this is #90098#. Bernard: the fix will be in the next OO build - 638 - I hope, but you might be waiting some time for this. If you want to get access to your document now, you can unzip the .sxw file and edit the content.xml stream. If you comment out the 3 lines with the text:anchor-page-number attribute, then you will be able to load and save your document. To comment something out in XML put <!-- before it and --> after it. If you can't or don't want to dit his, I could attach my version in which I did exactly that as an attachment to this bug.
Actually, I think it's sufficient to to set the anchor-page-number attribute from "0" to "1". This way, the document can be loaded but you don't loose the graphics.
Reassigned to Daniel.
Uuh, I goofed with committing the fix into the codebase; sorry guys! On a SRC638n (current CVS top-level), the documents load fine. (Some of the graphics seem jumbled, though.) Apparently, the original problem was in the WinWord import, and when re-loading the original file, the problem shouldn't occur any longer. The second (follow-on) problem was that OOo refuses to load documents with graphics anchored to page 0. This is now fixed, too. dvo->BG: Did you get your document back? dvo->sba: It should work on any build 638n or later.
Fixed on 638n (or later)
This task is fixed or worked in OOo 1.1 beta2.
closed ...