If part of the docx file is corrupted (altered or chopped) then writer can't open the file and can't repair the file. If file is fixed manually: # mkdir tmp # cd tmp # unzip file_corrupt.docx # zip -9r ../file_fixed.docx * Then writer opens file_fixed.docx (works, at least the most times) Why? Because lots of "docx" files contains images or not crucial information that can be "fixed" (a glitch is inevitable...) and get the file work again! Somebody give me a docx that was corrupted and i restored the file using this method ; Should be great if libreoffice check the file for corrupt and then try to restore the file (even if some part get glitched) ; Show "Warning! Some information should be inevitable lost" message will rock! For the problem file the command "unzip -t file.docx" give me this error: .... testing: word/embeddings/oleObject1.bin error: invalid compressed data to inflate file #9: bad zipfile offset (local header sig): 746694 (attempting to re-compensate) ...... And continue correctly all others files in file.docx Reproduce Error: * Create a docx whit some text and image * Using a Hex editor change some part of the file (string of 20 bytes or more) * Open libreoffice writer and crash! * Restore the file using the above method * Open libreoffice writer and works (the image get glitched, but you get all the information again, replace the image and go!) I found another related error! If you change Only 1 byte in docx file using a hex editor then the zip file get "slightly" corrupted whit this message in the test in the unzip command: # unzip -t file.docx .... testing: word/media/image1.jpeg bad CRC f13f46e1 (should be b4564b78) .... If you open with Writer then NO MESSAGE IS DISPLAYED, NO WARNING! NOTHING IS SHOW TO THE USER ; NO REPAIR PROCESS IS STARTED! Instead its open the file like is should be all "OK?" but you see the image is glitched (not all "OK!?"). I'am using: * Linux, Debian (unstable) * libreoffice-writer 1:5.0.5~rc1-1 * libreoffice 1:5.0.5~rc1-1 Sory my Bad Ingles :-P
Would be great, if you attached such an example here so testers can quickly test. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Sun, 11 Sep 2016 21:43:24 +0200
Created attachment 127320 [details] the file is corrupted but reparable spent some time; sorry for the delay For this attached file I generated the bug. The file can be repaired! unzip => zip => fixed! the file docx is corrupt in the picture! ( upper left corner ; see a little "line" ) I wanted to create an example but it is difficult, so sending the original .... Update: problem present in new version 1:5.2.0~rc3-1 (Debian testing)
I confirm Writer cannot repair it. Win 7 Pro 64-bit Version: 5.3.0.0.alpha0+ Build ID: ba269f7294e2416659011cbb498a2c6b5f9d5199 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-09-12_02:36:16 Locale: fi-FI (fi_FI); Calc: CL LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
Repro with: Version: 5.4.0.0.alpha0+ Build ID: b894104a0b02a9b074c76feb925389d7bee6a493 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-12-10_01:00:52 Locale: nl-NL (nl_NL); Calc: CL
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I would like to add that I have been getting a number of similar errors We are getting a number form letter style docx documents that appear to be generated by an earlier version of libreoffice to create form letters via a large government agency (ofsted). the app.xml shows the following <Properties xmlns="http://schemas.openxmlformats.org/officeDocument/2006/extended-properties" xmlns:vt="http://schemas.openxmlformats.org/officeDocument/2006/docPropsVTypes"><Template></Template><TotalTime>0</TotalTime><Application>LibreOffice/5.1.5.2$Windows_x86 LibreOffice_project/7a864d8825610a8c07cfc3bc01dd4fce6a9447e5</Application></Properties> unzipping and reziping the file fixes the problem, we normally just open in another program. the problem appears to affects openoffice and libreoffice 3.1-6.1 Word can open the files, wordonline can't. Pagis can't, WPS and Softmaker can. I thought it would be worthwhile posting as I unfortunatly can't share the documents due to confidentiality, but it may be a warning of an increasing frequency of this issue caused by some product on the market creating out of specification archives.
Dear Guillermo Reisch, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I confirm Writer cannot repair it. Linux goku 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64 GNU/Linux Debian SID ; libreoffice* 1:6.1.5-3 ; ure 6.1.5-3 ; LANG=es_UY.UTF-8 ; Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz lowering Importance... (minor)