#585 Libpng warning messages

[chris fahlman]

There are lots of warning messages from libpng when playing most scenarios.

These fill up the Aleph One log file or pollute the terminal.

If I run the following ImageMagick command to strip png metadata from the scenario and plugin files before running Aleph One, libpng doesn't complain and the log stays much cleaner.

find ./ -name "*.png" -exec mogrify -strip {} \;

Maybe the png Scenario files included with Alephone could be similarly cleaned to prevent all these messages?

Here's an example of the current output running Rubicon scenario and xbla hud:

alephone ~/Documents/MarathonStuff/marathonRubiconX/Rubicon\ X\ ƒ/
Aleph One Linux 2014-01-04 1.1
http://marathon.sourceforge.net/
{
.
.
.
}
GL_RENDERER: Mesa DRI Mobile Intel® GM45 Express Chipset
GL_VERSION: 2.1 Mesa 10.4.0
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
{...}

[Jeremiah Morris]

Incorrect color profiles have been stripped from the PNG files distributed with Aleph One 1.2 (20150619) and later. Note that only the Marathon trilogy is maintained by the Aleph One team: any errors from Rubicon or the Rubicon variant of the HUD will be unaffected. Unfortunately, libpng does not provide any way for Aleph One to suppress the messages.

If you still see libpng messages with the latest stock scenario files, please reopen this ticket and include details of your OS and your libpng version.