Summary: | FILEOPEN, FILESAVE, "Could not save document, error in writing sub document context.xml" then corrupt file. | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Marcool <tera_1225> |
Component: | Writer | Assignee: | Miklos Vajna <vmiklos> |
Status: | RESOLVED FIXED | QA Contact: | Jorendc <jorendc> |
Severity: | critical | ||
Priority: | medium | CC: | anton.balkin, courrier.oou.fr.mjk, dr.andonuts, embar, harald.koester, LibreOffice, lvilla, m.hudritsch, michael.meeks, mihhkel, Omar.w.kh, vmiklos, vstuart.foote |
Version: | 4.0.0.3 release | Keywords: | regression |
Hardware: | All | ||
OS: | All | ||
Whiteboard: | target:4.1.0 target:4.0.2 | ||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 54157 | ||
Attachments: | Example file |
Description
Marcool
2013-02-13 08:31:43 UTC
*** Bug 60997 has been marked as a duplicate of this bug. *** Because Anton reported a duplicate bug, we have a independent confirmation. Therefore I mark this bug as NEW. Anton reported this bug using windows, thus I change platforms to all. Kind regards, Joren Hi, I am just wondering, upon thinking about it a little more I have decided maybe this is in fact TWO bugs : -Number one, would relate to the error message I was getting on trying to save : "Could not save document, error in writing sub document context.xml" -Number two would relate to the fact that LO crashed with no output on trying to open that file later on. This one would then be connected to the OS X feedback I gave in the original bug post. I realize the two are no doubt related but I wonder if they are truly the same bug... probably not if looked at closely. Tell me what you think. Regards, Mark. Created attachment 75256 [details]
Example file
I got the same error message with version 4.0.0.3. I do not know if there is the same reason hence the description of Marcool is not really specific. Anton also wrote in bug 60997, that in his case the problem has something to do with comments with text ranges. So it seemed to me that my problem is at least similar to his problem. There are two other reports (bug 60133 and bug 60588) which deal with the same error message. May be these are also duplicates of this problem. I attached an example file in order to reproduce the bug. In order to reproduce the bug I did the following. If you use the example file start with step (7). (1) Open new text document. (2) Create three paragraphs. (3) Insert comment 1 (no text range) in Paragraph 1. (4) Insert comment 2 (text range: one word) in Paragraph 2. (5) Insert comment 3 (text range beginning in Paragraph 2 and ending in Paragraph 3). The part of the text range of Paragraph 2 is marked in blue, the part of Paragraph 3 is marked in yellow. Strange !!! (6) Save and close file (X). So far I prepared the example file which I will attach to this report. (7) Open file again. Now there are 2 “Comment 3”, one in Paragraph 2 and one in Paragraph 3 and both with no text range. Expected: Only one comment with text range !!! (8) Delete end of Paragraph 2 which is within the expected text range (in example file: Delete “Paragraph 2.”) (9) Try to save and close File (X). An error message is displayed: “Error saving the document <file name>: Write Error. Error in writing sub-document content.xml.” Expected: Save and Close document !!! (10) Klick OK and undo deletion. Then insert a word at the end of the Paragraph 3. (11) Save and close file (X). Now the file can be saved. OS: Win 7 Prof Oh..... I just saw that Bugzilla created links in my comment. This is not correct. The comments I mentioned should indicate comments inside a text document and not inside this bug report. Oh... and another mistake. I mentioned bug 60133. This is wrong, correct is bug 61033. (In reply to comment #5) > (5) Insert comment 3 (text range beginning in Paragraph 2 and ending in > Paragraph 3). The part of the text range of Paragraph 2 is marked in blue, > the part of Paragraph 3 is marked in yellow. Strange !!! This behaviour is reported in bug 61249. Same problem here, also after using comments. Marking critical, as it is a data-loss bug that cannot be avoided by regular saves. I have the same problem (WIN7 64), and a new symptom. I started selecting part of a text that's connected to a comment in order to remove it, Writer started saving endlessly, I tried sneaking in while it saves and clicked "Save As" but it resulted into the same problem (the content.xml error) then continued the endless saving loop, I had to close LibreOffice from the task manager. It could have been autosave stuck somehow because of this comments bug, there is no way for me to confirm this. If it wasn't clear, I recorded a video of the incident: http://youtu.be/4-9kk1GLrGM?t=7s I had the same looping problem once, but haven't been able to repeat it. Miklos - this looks rather bad - is it a duplicate of the comment mis-management bug we fixed in 4.0.1 ? I'd love feedback as to whether this continues in 4.0.1 or better 4.0.2rc1 available from http://www.libreoffice.org/download/pre-releases/ And apologies for the document corruption ! I can reproduce the bug using the steps from comment 5; at least odf export doesn't handle multi-para comments correctly, causing corrupted odf output. I'm looking into this. 100% [Reproducible] with Server Installation of "LibO 4.0.0.3 - GERMAN UI / German Locale [Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89)]" {tinderbox: @6, pull time 2013-01-31 11:30(?)} on German WIN7 Home Premium (64bit) with separate new User Profile: 1. Launch LibO 2. Open Copy of Sample "2013-02-21 15:23 UTC, harald-koester@htp-tel.de" 3. In third text line behind highlighted word behind following "2." click before "P" of next work "Paragraph" > Caret flashes before "P" 4. Keep left mouse button dragged and Select text until end of following text line > highlighted until trailing dot. 5. <Del> deletes highlighted Text 7. Menu 'File -> Close' > Dialog appears 8. Confirm with <Save> Bug: Message appears. This bug is no longer reproducible for me with 4.0.1.2 Let's see 4.0.1.2 results in "Bug 60588 - Error in writing content.xml" "Bug 61033 - FILESAVE: Write Error. Error in writing sub-document content.xml" @Miklós: If this WFM can be reproduced and you do not find hindering arguments we should close this one (if possible with hint concerning commit what fixed the problem). BTW, during my tests here I had a lot of crashes when I tried to save Attachment 75256 [details] or Attachment 74538 [details] for Bug 60588 from 4.0.0.3 after I had deleted some text behind Comment position marks. Also these crashes are no longer reproducible with 4.0.1.2 *** Bug 60588 has been marked as a duplicate of this bug. *** (In reply to comment #11) > > I'd love feedback as to whether this continues in 4.0.1 or better 4.0.2rc1 > available from http://www.libreoffice.org/download/pre-releases/ Had a Windows 7 64-bit system with 4.0.0.3 installed. Comment 4 attached document https://bugs.freedesktop.org/attachment.cgi?id=75256 error'd as reported. Installed 4.0.2.1 and with sample document have proper handling of text deletions with commenting present. Need to hear from OP of bug 61033 with details on if problem documents had commenting present with that issue Miklos Vajna committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=19802872052aaed9d3deff02b882b2043239a406 fdo#60769 implement odf export of multi-paragraph comment ranges The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -4-0 review: https://gerrit.libreoffice.org/2873 Miklos Vajna committed a patch related to this issue. It has been pushed to "libreoffice-4-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=473cd59a71706ada01f8be68c7dfd008ca9bb716&h=libreoffice-4-0 fdo#60769 implement odf export of multi-paragraph comment ranges It will be available in LibreOffice 4.0.3. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Miklos Vajna committed a patch related to this issue. It has been pushed to "libreoffice-4-0-2": http://cgit.freedesktop.org/libreoffice/core/commit/?id=7aa93e2c7c17e11f612bd4313e7c819aa49a9f26&h=libreoffice-4-0-2 fdo#60769 implement odf export of multi-paragraph comment ranges It will be available already in LibreOffice 4.0.2. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. I am not sure if this may somehow related, and you might want to check and see if the patch fixes the issue, but I have been noticing erratic behavior with comments showing up or disappearing from the navigation (F5) menu. I have a feeling (but have not checked), that this has something to do with paragraph breaks, and spaning comments. Nevertheless, of my hundred + comments, some show in navigator, some don't. Sorry this is poorly checked out or even specific, if I have some time I'll look into it more, but thought I'd better make a note here for you guys. Thanks for all the hard work, Regards, Mark. *** Bug 61033 has been marked as a duplicate of this bug. *** I got the same error on LO 4.1.3.2 on OSX 10.9. Win7 with the same LO can save the document. It has about 260 pages with lots of images and embedded objects. Has anyone a workaround. I don't want to go back to LO 3.6. Thanks Marcus Hi Marcus, Sorry, marking the bug as resolved once again. I just re-checked and in the original scenario (multi-pragraph commented text ranges) we are fine. Please take your 260 pages document, cut it down to a smaller document that still reproduces the problem, but trivial enough that you can make it public, create a new bugreport and attach the document there. Feel free to add me to CC of that bug, I'll try to have a look. Thanks, Miklos Hi Miklos, here is a link to my 40MB file. It is my computergraphics script that I teach: https://www.dropbox.com/s/v4zf2g4aexp1oc9/CanNotWriteBugOSX_LO4.1.3.2.odt I reproduce the bug 10 times. I have no addons installed. I use the latest OSX 10.9. Sorry for the size but I can not cut it down because I CAN NOT ANYMORE SAFE AT ALL! This is not critical. This is an absolut show stopper or blocker. I had to install LO 3.6.5 where it works perfectly. It also works on 4.1.3 under Windows. I left MS 5 years ago and won't go back anymore. Thanks for any help. Marcus Hi Marcus, (In reply to comment #25) > Sorry for the size but I can not cut it down because I CAN NOT ANYMORE SAFE > AT ALL! True, except you do unzip the .odt file and do it manually. /me isn't able to do that without destroying it completely. > This is not critical. This is an absolut show stopper or blocker. > I had to install LO 3.6.5 where it works perfectly. > It also works on 4.1.3 under Windows. I left MS 5 years ago and won't go > back anymore. Well, all good, but as Miklos Mentioned: create a new bug report for it and don't alter fields of this bug. Your bug has except for the same error text _nothing_ to do with this bug (code-wise). Therefore I did create a bug report for your problem myself: Bug 72129. Kind regards, Joren |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.