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