Bug 1121035 - libpng warning: Interlace handling should be turned on when using png_read_image
Summary: libpng warning: Interlace handling should be turned on when using png_read_image
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libpng
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Hracek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-18 08:44 UTC by Harald Reindl
Modified: 2016-01-06 12:17 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2016-01-06 12:17:27 UTC


Attachments (Terms of Use)

Description Harald Reindl 2014-07-18 08:44:02 UTC
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
how comes that "libpng" of RHEL7 brings back that problem not seen for many years? the log beloe is from httpd and so most like php with gd-library is the messenger

http://stackoverflow.com/questions/12990602/libpng-warning-interlace-handling-should-be-turned-on-when-using-png-read-image

libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image

Comment 2 Petr Hracek 2014-07-18 08:58:09 UTC
I will look at this bug.

Comment 3 Harald Reindl 2014-07-18 09:05:05 UTC
thank you!

it seems to come diect from libpng because any PHP oder httpd warning would have a date / time in the logs

these appears practically the same way as someone is calling a binary/script with exec() which produces stdout/stderr messages which all land in apaches errorlog

Comment 4 Petr Hracek 2014-07-18 09:54:22 UTC
I have looked at the libpng code and patch mentioned in upstream is included
in libpng-1.5.13 version too.

Do you have the same version?

How can I reproduce the error? Any suitable example?

I have browsed the libpng sources and the message is relevant only for this part of code.

Comment 5 Harald Reindl 2014-07-18 09:59:48 UTC
libpng-1.5.13-5.el7.x86_64

sadly since it's missing any timestamps i have no way to ask anybody what he may did and on what website - pretty sure the context is Magento webshop

if you can make a patch to include date/time in the message and provide me a binary RPM it should be easy to grep through the apache access logs which IP did what requests at the same time and find a reproducer

Comment 8 Petr Hracek 2016-01-06 12:17:27 UTC
As I have mentioned above the message comes from pngread.c file.
Upstream bug was already assigned http://sourceforge.net/p/libpng/bugs/165/
and it is already fixed in libpng-1.5.13-5 at least.

Please update to the latest one and let us know If the problem is still persistent.

I am closing the bug for now because I have not insufficient data.

Any reproducer would be welcome, though.


Note You need to log in before you can comment on or make changes to this bug.