GNOME Bugzilla – Bug 782307
gresource icons in easytag broken since 2.36.1
Last modified: 2017-07-05 20:42:05 UTC
https://bugs.launchpad.net/ubuntu/+source/easytag/+bug/1689033 When gdk-pixbuf >= 2.36.1 is installed, all the icons stored in the gresources of easytag show up as the "image missing" icon. There is an image in the above Ubuntu bug. I checked the released versions of gdk-pixbuf. Using 2.36.0 works properly and all versions since then are broken. If I remove all the "preprocess='to-pixdata'" attributes from the resources xml file and rebuild easytag, the images work again. https://git.gnome.org/browse/easytag/tree/data/org.gnome.EasyTAG.gresource.xml While looking at this I noticed that all the images in /org/gtk/libgtk/theme/Adwaita/assets in the GtkInspector look broken as well (all displaying the "image missing" icon).
Please test with the current stable version, this problem has been fixed in 2.36.2 (bug 776105).
It is not working on F26 with gdk-pixbuf2-2.36.6-1.fc26.x86_64 installed, nor in master (jhbuild environment built yesterday). All the easytag image resources created using to-pixdata show up as the "image missing" icon in the inspector, although the inspector's resources (under /org/gtk/libgtk/theme/Adwaita/assets) work fine.
The test for this is working fine: https://git.gnome.org//browse/gdk-pixbuf/tree/tests/resources.gresource.xml https://git.gnome.org//browse/gdk-pixbuf/tree/tests/pixbuf-resource.c So we'd need a minimal reproducer. Running: G_MESSAGES_DEBUG=all easytag should show you GdkPixbuf-DEBUG messages related to loading pixdata, but it seems that easytag eats envvars. You can also try adding debug to gdk-pixbuf's _gdk_pixbuf_new_from_resource_try_pixdata() especially the gdk_pixdata_deserialize() and gdk_pixbuf_from_pixdata() calls to see if they throw errors.
I'm guessing it's used via GTK+, not in gdk-pixbuf directly, so might be bug 781583. Same request about a test case though.
I tested a slightly different patch to yours for bug 781583 and the icons worked again, so it does look likely to be that bug in GTK+.
*** This bug has been marked as a duplicate of bug 781583 ***