Hi, On 23-05-2013 10:28, pgajdos@suse.cz wrote:
Hi List,
JFYI, libpng 1.6.2, which is currently in factory can introduce fails when reading png, namely 'IDAT: invalid distance too far back'.
See e. g. multimedia:apps/lilypond build for factory. Very probably, these images will not read anymore with newer libpngs.
For multimedia:apps/lilypond example, there are 195 png images, only three fails to read.
It is possible to use optipng to fix them or wait for 1.6.3, which will ship png-fix-too-far-back tool (see graphics/libpng17). I am going to create corresponding rpm macro to find and fix these PNGs in a package, where it is called.
Again, these PNGs are said to be broken; they should be fixed upstream. If I've understood correctly, not supporting them should help libpng to be more memory-efficient.
Further reading & links: https://git.reviewboard.kde.org/r/110314/
Unrelated to this, in Mono:Community/keepass we are getting libpng error: invalid after png_start_read_image or png_read_update_info Any idea about this one? Thanks. -- SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org