** THIS IS NOT FIXED - iCCP: known incorrect sRGB profile **

[VBoxGrl]

There were two tickets on this in the past that closed this as a defect or a fix: #12807, #12610.

With the latest version of libpng 1.6x I found out that in VirtualBox 5.0.26 one of the png files that comes in the source has the problem, it's not a problem in someone's system.

Oracle you need to fix your png that you ship with VirtualBox!

If Oracle hasn't fixed this in 5.1 then the problem still exists.

I ran this cmd in the source directory;

find . -type f -name "*.png" -exec convert {} -strip {} \;

Then I recompiled VirtualBox 5.0.26 and the message was gone!

[Klaus Espenlaub]

Could you tell us which file(s) are causing the issue? It's very difficult to find a Linux distro which comes with libpng 1.6 (and especially an ImageMagick package which uses it), otherwise we'd find out ourselves.

[Klaus Espenlaub]

We tried finding the file ourselves, but failed. We used ImageMagick with libpng 1.6, but there was nothing on stderr...

[VBoxGrl]

1.6 happens to be the latest version of libpng and there are distros that do use it;

​http://www.libpng.org/pub/png/libpng.html

I do not know what image is the problem, I didn't look into which one(s). It is the image(s) packed with the Virtualbox source causing this, it is not a image on the distro side...

If you use Slackware 14.2 and check 5.0.26 you will see the problem and maybe it will help you, at least I know with this distro and VB version you can see the problem...

[Valery Ushakov]

Sorry, but we did check with the latest libpng and couldn't find anything problematic. We might be wrong, but that is what we know so afar, so please, don't reopen unless you can tell which files caused problems for you.

[VBoxGrl]

I'm not the VB developer and I didn't rip through the source either to try and figure out what images are embeded into Virtualbox.

It's whatever images are embeded into VirtualBox that it uses, not complicated.

I compiled and ran 5.0.26 and this appear in the output;

iCCP: known incorrect sRGB profile

I went into the top level of the source and ran;

find . -type f -name "*.png" -exec convert {} -strip {} \;

Then I recompiled it and the message was gone, simple.

It's not complicated, you are the developers, to figure out, not me, I just found the problem...

[Valery Ushakov]

Replying to VBoxGrl:

It's not complicated, you are the developers, to figure out, not me, I just found the problem...

If it's not complicated, why do you refuse to help?

We did run identify -verbose on all png images (with image magic linked against the latest libpng 1.6.23) and didn't get any errors. May be we messed up, but we don't see the problem. You do. So, please, can you run it on the original sources with unstripped images and tell us which file fails for you?

[VBoxGrl]

I ran this in the src direc and it didn't find anything;

find . -name '*.png' -exec identify {} \; 1>/dev/null 2>files

I only see the problem when running VirtualBox, something appears to be happening to the image(s) that get embeded into VirtualBox and that I wouldn't be able to figure out, as I'm not the coder/developer...