tag 690066 + moreinfo thanks Hi,
On Tue, Oct 09, 2012 at 01:07:41PM -0300, David Bremner wrote: > Package: libreoffice-writer > Version: 1:3.5.4+dfsg-2 > Severity: grave > Justification: causes non-serious data loss oh, no. And that for that docx.... "Thankfully" we had #620137 once and so this isn't a regression... > The corruption actually does not rely on editing the file; this can be > confirmed using "save-as" to a second docx file; the same apparent > truncation happens. > > Unzipping the truncated file, it looks like the user data (i.e. text > of paragraphs) is actually still there, but according to xmllint > word/document.xml does not parse. > > word/document.xml:2: parser error : Opening and ending tag mismatch: > hyperlink line 2 and p > ="18"/><w:szCs w:val="20"/></w:rPr><w:t xml:space="preserve"> > </w:t></w:r></w:p> > > ^ > word/document.xml:2: parser error : Opening and ending tag mismatch: p > line 2 and body > docGrid w:charSpace="0" w:linePitch="360" > w:type="default"/></w:sectPr></w:body> > > ^ > word/document.xml:2: parser error : Opening and ending tag mismatch: body > line 2 and document > rSpace="0" w:linePitch="360" > w:type="default"/></w:sectPr></w:body></w:document> > > ^ > word/document.xml:2: parser error : Premature end of data in tag document > line 2 > rSpace="0" w:linePitch="360" > w:type="default"/></w:sectPr></w:body></w:document> > > I suppose it might in principle be possible to recover the data from > the corrupted XML file. That seems daunting enough that it still seems > to be an RC bug to me. I actually don't believe this is a RC bug; but I'll not argue. Just quickly discussed it with upstream: 18:21 <@_rene_> sigh. 18:21 <@_rene_> anyone seen http://bugs.debian.org/690066 yet? 18:22 <@shm_get> Sweetshark pong 18:27 < MechtiIde> _rene_, I have seen such things 18:28 < MechtiIde> also at other plattforms 18:29 * _rene_ is actually more interested in whether we have a fix already... 18:29 <@_rene_> but thanks :) 18:30 <@vmiklos> _rene_: fdo#53175 looks similar and it's fixed already 18:30 -!- jchaffraix [julien@nat/google/x-ziyrpcgdnnjmchcu] has joined #libreoffice-dev 18:30 < IZBot> LibreOffice-Writer critical/medium RESOLVED FIXED FILEOPEN error reading “Content (TOC)” from a DOCX https://bugs.freedesktop.org/show_bug.cgi?id=53175 18:30 -!- jchaffraix [julien@nat/google/x-ziyrpcgdnnjmchcu] has quit [Changing host] 18:30 -!- jchaffraix [julien@pdpc/supporter/bronze/jchaffraix] has joined #libreoffice-dev 18:30 <@vmiklos> not sure if it got picked to -3-5. 18:32 <@_rene_> vmiklos: how do you see it? The commit message just says hyperlinks and the topic TOC. how is it this bug? (just for understanding) 18:33 <@_rene_> ah, the attachment? 18:33 <@vmiklos> _rene_: i guess in both cases the exporter deals with fields, and for some reason the field tag was started, but not ended 18:33 <@vmiklos> _rene_: i guess in both cases the exporter deals with fields, and for some reason the field tag was started, but not ended 18:34 <@vmiklos> resulting in invalid xml, Word barking correctly. 18:35 <@vmiklos> the bug title says import, but the problem was in the exporter. 18:36 <@vmiklos> fdo#47669 may be also related. 18:36 < IZBot> LibreOffice-Writer major/high ASSIGNED Bad processing hyperlink with anchor in DOCX https://bugs.freedesktop.org/show_bug.cgi?id=47669 18:37 <@_rene_> this will be interesting I fear if I need to backport it to 3.5.4... 18:38 <@vmiklos> well, if backporting is the only problem, poke me next week and i'll give it a try, i don't think this part of the code changed too much. 18:40 <@_rene_> ok, I'll first ask him to get me a sample file and will try myself Have some example file? I thankfully don't have docx'es here... Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org