Your message dated Mon, 4 Aug 2014 21:45:48 +0200 with message-id <20140804194548.gc15...@rene-engelhard.de> and subject line Re: Bug#690066: libreoffice-writer: silently corrupts docx file has caused the Debian Bug report #690066, regarding libreoffice-writer: silently corrupts docx file to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 690066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libreoffice-writer Version: 1:3.5.4+dfsg-2 Severity: grave Justification: causes non-serious data loss The data loss scenario is as follows: 1) Open the attached docx file, 2) Edit it, save as docx. The file is now un-openable by MS Office, and only the first 3 pages are visible in libreoffice. 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. FWIW, I get this message in the terminal where I started lowriter /tmp/buildd/libreoffice-3.5.4+dfsg/writerfilter/source/dmapper/GraphicImport.cxx:1486 failed. Message :GraphicCrop -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libreoffice-writer depends on: ii libc6 2.13-35 ii libgcc1 1:4.7.1-7 ii libicu48 4.8.1.1-9 ii libreoffice-base-core 1:3.5.4+dfsg-2 ii libreoffice-core 1:3.5.4+dfsg-2 ii libstdc++6 4.7.1-7 ii libwpd-0.9-9 0.9.4-3 ii libwpg-0.2-2 0.2.1-1 ii libwps-0.2-2 0.2.7-1 ii libxml2 2.8.0+dfsg1-5 ii uno-libs3 3.5.4+dfsg-2 ii ure 3.5.4+dfsg-2 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages libreoffice-writer recommends: ii default-jre [java5-runtime] 1:1.6-47 ii libreoffice-emailmerge 1:3.5.4+dfsg-2 ii libreoffice-filter-binfilter 1:3.5.4+dfsg-2 ii libreoffice-java-common 1:3.5.4+dfsg-2 ii libreoffice-math 1:3.5.4+dfsg-2 ii openjdk-6-jre [java5-runtime] 6b24-1.11.4-3 Versions of packages libreoffice-writer suggests: pn libreoffice-base <none> pn libreoffice-gcj <none> Versions of packages libreoffice-core depends on: ii fontconfig 2.9.0-7 ii fonts-opensymbol 2:102.2+LibO3.5.4+dfsg-2 ii libc6 2.13-35 ii libcairo2 1.12.2-2 ii libcmis-0.2-0 0.1.0-1+b1 ii libcurl3-gnutls 7.26.0-1 ii libdb5.1 5.1.29-5 ii libexpat1 2.1.0-1 ii libexttextcat0 3.2.0-2 ii libfontconfig1 2.9.0-7 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.1-7 ii libglib2.0-0 2.32.3-1 ii libgraphite2-2.0.0 1.1.3-1 ii libgstreamer-plugins-base0.10-0 0.10.36-1 ii libgstreamer0.10-0 0.10.36-1 ii libhunspell-1.3-0 1.3.2-4 ii libhyphen0 2.8.3-2 ii libice6 2:1.0.8-2 ii libicu48 4.8.1.1-9 ii libjpeg8 8d-1 ii libmythes-1.2-0 2:1.2.2-1 ii libneon27-gnutls 0.29.6-3 ii libnspr4 2:4.9.2-1 ii libnspr4-0d 2:4.9.2-1 ii libnss3 2:3.13.6-1 ii libnss3-1d 2:3.13.6-1 ii libpng12-0 1.2.49-1 ii librdf0 1.0.15-1+b1 ii libreoffice-common 1:3.5.4+dfsg-2 ii librsvg2-2 2.36.1-1 ii libsm6 2:1.2.1-2 ii libssl1.0.0 1.0.1c-4 ii libstdc++6 4.7.1-7 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxinerama1 2:1.1.2-1 ii libxml2 2.8.0+dfsg1-5 ii libxrandr2 2:1.3.2-2 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.26-14 ii uno-libs3 3.5.4+dfsg-2 ii ure 3.5.4+dfsg-2 ii zlib1g 1:1.2.7.dfsg-13 -- no debconf information
bar.docx
Description: MS-Word document
--- End Message ---
--- Begin Message ---Version: 1:4.2.1-1 Hi, On Mon, Aug 04, 2014 at 09:01:49PM +0200, Nicolas Boulenguez wrote: > Package: libreoffice-writer > Followup-For: Bug #690066 > Control: fixed -1 1:4.2.5-1+b1 > > Hello. > This bug is fixed in 1:4.2.5-1+b1, and has apparently been for a while > according to the upstream forwarded bug log. It says 4.2.0. So let's close it with 1:4.2.1-1 which is the first 4.2.x in the changelog. That also has the effect that it's marked as fixed in 4.3.x, too (4.2.5-1 is on an other branch, so a fixed there doesn't exactly tell whether it works in 4.3.x...) > You may want to close it. Doing with this. Regards, Rene
--- End Message ---
