There seems to be a class of PNG images that LibO cannot load anymore (but OOo can). See attached bugdoc.
Created attachment 42874 [details] bugdoc
the main difference between working and errornous pictures are in the IHDR chunk of the file. If the colortype byte is 6, the file works, if it is 2, it dosnt work. In the specification (http://www.libpng.org/pub/png/spec/1.2/PNG-Chunks.html#C.IHDR) stand: Color Allowed Interpretation Type Bit Depths 2 8,16 Each pixel is an R,G,B triple. 6 8,16 Each pixel is an R,G,B triple, followed by an alpha sample. If you open the errornous file with MS Paint and save it again, it works.
[Reproducible] with "LibreOffice 3.3.0 RC4 - WIN7 Home Premium (64bit) German UI [OOO330m19 (build 6 / tag 3.3.0.4)]" It's not a WRITER, but a general problem. I extracted the picture 100000000000007400000060D55E1F69.png If you try to insert it to a DRAW document or to open it with DRAW, you will get some filter error message ("Grafikfilter nicht gefunden"). No Problem with OOo 3.1.1, 3.4-dev and 1.4.1 (!) I am pretty sure that all OS will be affected, but currently information is missing. @all: What OS did you use for your test?
Created attachment 42890 [details] sample image, see Comment 3
I testet it with Win 7 and sUse 1.3, it is OS independ.AMD64 and x86
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
reproduced in LibO 3.5.0 beta 2 on Fedora 64 bit some other experiment done: MSWord 2007 on Windows XP opens this file with part of picture, MSWord 2010 on Windows 7 opens all correctly if extract picture from odt file: Gimp opens part of picture on Windows and Linux MSWord 2003 and default picture viewer on Windows opens picture correctly if drag and drop picture to LibO, it creates new section (not recognizes file as picture)
Not sure whether this adds any useful information, but : on Mac OSX, LibO 3.5RC1 1) I open a ODT document made with LIbO 3.3.x containing an *inserted* (not linked) PNG file in it (for example, my signature, which has alpha channel), the image frame holder displays an error and the PNG file is not shown. 2) If I then save that document in 3.5RC1, and then attempt to open it again in 3.3.4, for example, I get an general IO error message, and the document will not open. If I retry once more, the document will open, but the image file is now missing. 3) Once I re-insert the same PNG file via 3.3.4, the same ODT file opens fine in : LibO 3.3.4 LibO 3.4.3 LibO 3.4.4 LibO-dev 3.5.0 Build ID: e42dfec-c60ac25-41e7bcd-3b66bd0 LOdev 3.6.0 Build ID: 87ec1f8-b204871-95bcc5e-4c1bcb5 and also LibO 3.5RC1, but the fact remains that the first time such a file is opened, it can not read the PNG file. Somehow, the reference to the file seems to get broken, despite it being inserted. Quite possibly, this is not the same problem as the bug report. Alex
Confirmed with: Version: 4.2.0.0.alpha0+ Build ID: 087a610fcd5c0c354a9ed6bfccd3451b667d62a3 TinderBox: Win-x86@6-debug, Branch:master, Time: 2013-08-04_21:41:24 Windows 8.1 Enterprise Preview 64 bit Picture is still not displayed. All good in Word 2013.
I don't know if it may help since I don't know how to test a newer libpng version but last libpng version is 1.6.6 (see http://download.sourceforge.net/libpng/libpng-1.6.6.tar.gz). Now of course there could be some API incompatibilities.
** 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 on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
Still read error. Win 7 Pro 64-bit Version: 5.0.0.0.alpha1+ (x64) Build ID: f3375fa07f27bd2ade519af3c07d69040d10eaa9 TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-22_23:38:50 Locale: fi_FI
If this is an issue with libpng, which one did work back then ? Last version that worked for me is Go-OO 3.2.0. LO 3.3.4 under win7 didn't work any longer. Tried different programs, but just a few worked (all microsoft programs), read: loading the extracted sample correctly. Works: IE11, paint, windows photo viewer. Doesn't work: VLC, Media player classic, xnview, Firefox, palemoon, opera dev (just loads the top). Even online converters can't convert them. Seems that all of these last programs have updated their libpng or else microsoft found a way to load these images. When I use pngtest I get the outcome: 'Pass 0: rwrwrwrwrwrwrwrwrwrwrwrwrwrwrw1.png: libpng warning: IDAT: invalid distance too far back libpng error: IDAT: invalid distance too far back' When I use pngfix it says: 'In particular the zlib error: "invalid distance too far back" caused by an incorrect optimization of a zlib stream is fixed in any compressed chunk in which it is encountered. An integrity problem of the PNG stream caused by a bug in libpng which wrote an incorrect chunk length is also fixed.' So it could be an error in zlib or an error in libpng or a bit of both. Maybe the correct way of handling these files are to fix them instead of trying to fix the code.
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Confirmed on Version: 5.3.0.0.alpha1+ Build ID: bb50b1609abe83265311613db4a18e992dc666c8 CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; Layout Engine: new; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-11-14_23:25:25 Locale: nl-NL (nl_NL); Calc: CL
(In reply to Telesto from comment #15) > Confirmed on > Version: 5.3.0.0.alpha1+ > Build ID: bb50b1609abe83265311613db4a18e992dc666c8 > CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; Layout Engine: > new; > TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-11-14_23:25:25 > Locale: nl-NL (nl_NL); Calc: CL It's still confirmed coz it's (probably) a libpng problem. The author won't/can't fix it, because he wants to move on with the code (or that's how I read it). The changes that have been made to the code is that the 'too-far-back' isn't shown anymore, but not to read the older files. Read some more here: https://bugzilla.mozilla.org/show_bug.cgi?id=841734#c9 So maybe it's better to fix the png's instead ?!
** 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
Thank you for reminding me to leave CC list.
(In reply to MM from comment #16) > So maybe it's better to fix the png's instead ?! I think you are right. A developer even wrote a handy utility to fix all the broken pngs on one's computer: http://archscientist.altervista.org/blog/how-to-solve-libpng-error-idat-invalid-distance-too-far-back/