GNOME Bugzilla – Bug 697286
libpng 1.6 cannot load nm-applet icons
Last modified: 2013-04-18 13:19:21 UTC
WARNING **: Icon nm-signal-75 missing: (0) Fatal error reading PNG image file: Decompression error in IDAT WARNING **: Icon nm-signal-75 missing: (0) Fatal error reading PNG image file: Decompression error in IDAT I have bunch of these in my logs. Previously I have rebuilt everything against libpng 1.6.1.
See also http://sourceforge.net/mailarchive/message.php?msg_id=30702058
Created attachment 241062 [details] re-saved version of nm-signal-75.png does this file give the same errors or does it work?
The problem is in whole icon set, including -100, -50, -25 and -0. I can't tell untill my signal gets to 75% ... Some post in the thread I linked to tells how to fix the icons I think.
presumably anything linked to libpng 1.6 ought to fail in the same way as nm-applet did. eg, if you try to view the icon in epiphany, or open it in eog. (Try with one of the ones in /usr/share/icons/hicolor/22x22/apps/ first to see if you get the error, then try with the one attached here.) I realize the bug affects all of them, I just don't want to commit "fixed" versions without verifying that they're actually fixed first, and I can't easily test that myself.
For the one in /usr/share/icons/hicolor/22x22/apps/ EOG can't open it - same error message as before. Firefox can partially load it - not the whole icon. The attached one appears to render correctly in Firefox and EOG. Everything is linked against libpng 1.6.1
(In reply to comment #3) > The problem is in whole icon set, including -100, -50, -25 and -0. Hm "whole icon set" as in "all the signal icons", or as in "every icon in nm-applet"? Eg, do the "connecting" icons with the green dots and the spinning whirls display correctly, or do you get errors about those too?
Sorry, by whole set I meant whole nm-signal-xx.png set. nm-signal-100.png nm-signal-75.png nm-signal-50.png nm-signal-25.png nm-signal-00.png
fixed in master and nma-0-9-8
All of them work fine now. I hope we will soon see a bugfix release including them. Thanks for the quick response.
*** Bug 698286 has been marked as a duplicate of this bug. ***