Error: Lossy operations are not currently supported

[binarykitchen]

Yesterday that error wasn't here. But today. What does this mean?

Running "imagemin:png" (imagemin) task
Warning: ** Error: Lossy operations are not currently supported
 Use --force to continue.

[kevva]

I've no idea. It's an error outputted from optipng.

[jamesplease]

@binarykitchen their issue tracker is here.

[binarykitchen]

Ok I will ask there. But I think since this module relies heavily on optipng, it concerns everyone of us here.

[binarykitchen]

Okay, reported in https://sourceforge.net/p/optipng/bugs/44/

[vladikoff]

@binarykitchen code snippet might help https://github.com/Juntalis/PyOptiPng/blob/master/src/optipng.c#L715

[binarykitchen]

@vladikoff I've seen it too but it doesn't tell me much. No hint on how to solve it, what the cause it etc.

Look, I did not touch my PNG files nor program code this week and then suddenly this happened. All I did is an npm update over many packages. Weird.

[vladikoff]

@binarykitchen clear the old PNGs, try optimizing with the new version of the plugin, 0.6.0 ?

[ctruta]

The resolution to this error is using an OptiPNG version that supports the option "-strip=all". The earliest version that supports this option is 0.7 (although using that old version is not recommended, because of other defects). The recommended stable versions are either 0.7.4 or 0.7.5.

Thank you very much for using OptiPNG :-)

[vladikoff]

@ctruta hey, we use 0.7.4 from https://github.com/yeoman/node-optipng-bin#node-optipng-bin-

[ctruta]

@vladikoff The "lossy operations not supported" error message exists in the 0.6.x line only. It was removed from version 0.7, when the option -strip got implemented. I guess you might pick up an older OptiPNG version accidentally from somewhere else in your $PATH?

[kevva]

Do you have OptiPNG installed globally?

[binarykitchen]

Thanks guys for your comments. Hmmm, with the new version 0.6.0 I get a new error:

Fatal error: Cannot find module 'pngquant-bin'

[binarykitchen]

Also, I found in another grunt task for JPG files only that any JPG file becomes corrupted :(

[binarykitchen]

@kevva No, I do not have OptiPNG installed globally

[kevva]

@binarykitchen, that's weird because the version we provide is 0.7.4

[binarykitchen]

Windoze? I am on Linux. Has anyone tested the latest package on Linux yet?

[kevva]

Oh, was under the impression you was on Windows. Just ran it on Linux (Ubuntu) and everything worked smoothly. Also Travis is Linux too and tests are passing fine there.

Try npm cache clean and install again.

[binarykitchen]

Hah, I made that impression? Lol ...

Ok, I'll try to clean the npm cache tomorrow at work. Ta!

[kevva]

Nah, not you. But most problems seems to come from Windows users so I just assumed you were one of them ;pp.

[ctruta]

@binarykitchen just a guess: are you, by any chance, using Debian, or a Debian-based distro? The stock OptiPNG that comes with Debian was still at version 0.6.4, last time I checked. Maybe you had that version installed, indirectly?

[binarykitchen]

nope, using ubuntu 13 here

[kevva]

Does which optipng give you anything?

[ctruta]

@binarykitchen ah, Ubuntu, that's definitely Debian-based, and Ubuntu 13.x ships OptiPNG version 0.6.4.

[binarykitchen]

At work now on Ubuntu 13:

$ which optipng
/usr/bin/optipng

and

$ optipng
OptiPNG 0.6.4: Advanced PNG optimizer.
Copyright (C) 2001-2010 Cosmin Truta.
...

So, what now?

[kevva]

So you have a global install after all. Just update it to a new version.

[binarykitchen]

Okay, works now after recompiling optipng according to
http://kb.imakewebsites.ca/2012/10/16/installing-optipng-0-7-3-on-ubuntu-12-04/

But what happens when I deploy the code on the server? :(

Too bad apt-get does not install/update optipng anymore ...

[binarykitchen]

Hmmm, there is a new problem: JPEG images are corrupted! When I try to open these in the image viewer I see this error message "Error interpreting JPEG image file (Improper call to JPEG library in state 200)"

[binarykitchen]

@kevva Ummm, I am having these issues again after installing a new machine.

I wonder why you guys aren't adding https://github.com/yeoman/node-optipng-bin to package.json?

[morgoth]

I had the same problem.
I'm on Ubuntu 14.04.
I removed optipng from my system and it works now.

[Misterhex]

@binarykitchen +1 for adding https://github.com/yeoman/node-optipng-bin to package.json, worked for me on ubuntu 14.04