On 18/04/13 21:38, Ian Stakenvicius wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/04/13 02:24 PM, Samuli Suominen wrote:
Short version:
If you see "PNG IDAT errors" like:
program: IDAT: invalid distance too far back `test1.png' @
WARNING **: Icon test1 missing: (0) Fatal error
On 18/04/13 21:24, Samuli Suominen wrote:
Short version:
If you see "PNG IDAT errors" like:
program: IDAT: invalid distance too far back `test1.png' @
WARNING **: Icon test1 missing: (0) Fatal error reading PNG image file:
Decompression error in IDAT
Many of the KDE icons won't display anymo
On Mon, Apr 15, 2013 at 11:54:22AM -0700, Gregory M. Turner wrote:
> On 4/15/2013 10:31 AM, Steven J. Long wrote:
> > On Mon, Apr 15, 2013 at 12:01:24PM +0100, Ciaran McCreesh wrote:
> >> The spec guarantees that ROOT will be non-empty and end in a slash. If
> >> Portage isn't enforcing this, file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/04/13 02:24 PM, Samuli Suominen wrote:
> Short version:
>
> If you see "PNG IDAT errors" like:
>
> program: IDAT: invalid distance too far back `test1.png' @
>
> WARNING **: Icon test1 missing: (0) Fatal error reading PNG image
> file: Decom
Short version:
If you see "PNG IDAT errors" like:
program: IDAT: invalid distance too far back `test1.png' @
WARNING **: Icon test1 missing: (0) Fatal error reading PNG image file:
Decompression error in IDAT
Then you should use >=media-gfx/pngcrush-1.7.57 built with
USE="-system-libs" to i