All,
Running kmenuedit from the command line, I received the following:
15:05 valkyrie:~> kmenuedit 15:05 valkyrie:~> libpng warning: Interlace handling should be turned on when using png_read_image
Is that something that needs to be addressed? Or, is that just a message that can be turned on/off?
Running kmenuedit from the command line, I received the following:
15:05 valkyrie:~> kmenuedit 15:05 valkyrie:~> libpng warning: Interlace handling should be turned on when using png_read_image
Is that something that needs to be addressed? Or, is that just a message that can be turned on/off?
I'm running GIT within the past day or so and I don't see that message when running from konsole.
Darrell
Running kmenuedit from the command line, I received the following:
15:05 valkyrie:~> kmenuedit 15:05 valkyrie:~> libpng warning: Interlace handling should be turned on when using png_read_image
Is that something that needs to be addressed? Or, is that just a message that can be turned on/off?
I'm running GIT within the past day or so and I don't see that message when running from konsole.
Note: I'm not building with gcc 4.7 or libpng 1.5. Perhaps we need a libpng 1.5 patch for kmenuedit?
Darrell
On 06/06/2012 08:35 PM, Darrell Anderson wrote:
Note: I'm not building with gcc 4.7 or libpng 1.5. Perhaps we need a libpng 1.5 patch for kmenuedit?
Darrell
I think that is the case. However, this doesn't cause unexpected behavior and it isn't a build error such as the direct access to the png_info struct, etc.. I don't know what is causing it, but we do need to clean it up. All of the stray 'warnings' are telling us that something is not right. I'm always suspicious that 'warning1 + warning2 = unforeseen errors'.
What does this mean:
libpng warning: Interlace handling should be turned on when using png_read_image
Is something not started or initialized before a call to png_read_image? I'll google around, if you already have the answer, let me know...
I think that is the case. However, this doesn't cause unexpected behavior and it isn't a build error such as the direct access to the png_info struct, etc.. I don't know what is causing it, but we do need to clean it up. All of the stray 'warnings' are telling us that something is not right. I'm always suspicious that 'warning1 + warning2 = unforeseen errors'.
What does this mean:
libpng warning: Interlace handling should be turned on when using png_read_image
Is something not started or initialized before a call to png_read_image? I'll google around, if you already have the answer, let me know...
I don't know. Have you tried "strace -o" and then search the strace output file?
I have a basic idea how to create a libpng 1.5 patch as we did previously. If you find any clues we can work together to cobble together a patch. But I can't test for libpng 1.5 because Slackware Current is at 1.4.9.
Darrell
-
Darrell Anderson -
David C. Rankin