| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 18/04/13 02:24 PM, Samuli Suominen wrote: |
| 5 |
> Short version: |
| 6 |
> |
| 7 |
> If you see "PNG IDAT errors" like: |
| 8 |
> |
| 9 |
> program: IDAT: invalid distance too far back `test1.png' @ |
| 10 |
> |
| 11 |
> WARNING **: Icon test1 missing: (0) Fatal error reading PNG image |
| 12 |
> file: Decompression error in IDAT |
| 13 |
> |
| 14 |
> Then you should use >=media-gfx/pngcrush-1.7.57 built with |
| 15 |
> USE="-system-libs" to it's using libpng 1.5.15 to correct the IDAT |
| 16 |
> in the .png files using command: |
| 17 |
> |
| 18 |
> $ pngcrush -fix -force old.png new.png |
| 19 |
> |
| 20 |
> These bogus images were visible with libpng15 and earlier but now |
| 21 |
> that improved code was committed these bogus files stopped showing |
| 22 |
> as a side-effect. If I understood correct this is not going to be |
| 23 |
> fixed in the library itself. Caused by slightly bad combination of |
| 24 |
> libpng and zlib and some tool. |
| 25 |
> |
| 26 |
> Long version: |
| 27 |
> |
| 28 |
> http://bugs.gentoo.org/466190 |
| 29 |
> http://bugzilla.gnome.org/show_bug.cgi?id=698286 + the ML links |
| 30 |
> mentioned in the bugs |
| 31 |
> |
| 32 |
> Figured this is useful for every maintainer to know. |
| 33 |
> |
| 34 |
|
| 35 |
|
| 36 |
Is this related to the mozilla issue too? ie, should the mozilla herd |
| 37 |
just fix and supply a 'loading' icon until upstream updates theirs? |
| 38 |
|
| 39 |
|
| 40 |
-----BEGIN PGP SIGNATURE----- |
| 41 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 42 |
|
| 43 |
iF4EAREIAAYFAlFwPbcACgkQ2ugaI38ACPBmfwD7BIgai/x6GWiGC9KWY7cidnLW |
| 44 |
jqwc4BbEnYsHfq7DiAIA/Rny5+nmqiszE6GVYmpX17VP6G6RRsg7hzKRLvW7luIJ |
| 45 |
=pr0x |
| 46 |
-----END PGP SIGNATURE----- |
Archives