@jazzynico - is there a need to add bug tasks for inkscape-devlibs and inkscape-devlibs64, and to track it as 'Triaged' for project Inkscape until Windows builds of Inskcape ship with a new enough version of gdk-pixbuf which includes this fix?
With regard to Inkscape packages for OS X: I don't think we would have to keep this report open specifically for those. They already use the unstable 2.31.x series of upstream gdk-pixbuf releases (0.91 has 2.31.2, most recent devel snapshot builds (0.91+devel) have 2.31.6, the next one to be uploaded will have 2.31.7), and any future stable release package (be it for 0.91.1, or 0.92) will include the latest available version at the time (unstable or stable, whatever is newer).
(The test case based on which this report was filed is AFAIU a handcrafted PNG file - I do not know how many such files are encountered by Inkscape users in daily usage).
Upstream fix available in latest gdk-pixbuf release (2.31.7) /git.gnome. org/browse/ gdk-pixbuf/ commit/ ?id=ca3c56421c0 75e729750cf80c3 438b283232cce8
Related upstream commit:
https:/
@jazzynico - is there a need to add bug tasks for inkscape-devlibs and inkscape-devlibs64, and to track it as 'Triaged' for project Inkscape until Windows builds of Inskcape ship with a new enough version of gdk-pixbuf which includes this fix?
With regard to Inkscape packages for OS X: I don't think we would have to keep this report open specifically for those. They already use the unstable 2.31.x series of upstream gdk-pixbuf releases (0.91 has 2.31.2, most recent devel snapshot builds (0.91+devel) have 2.31.6, the next one to be uploaded will have 2.31.7), and any future stable release package (be it for 0.91.1, or 0.92) will include the latest available version at the time (unstable or stable, whatever is newer).
(The test case based on which this report was filed is AFAIU a handcrafted PNG file - I do not know how many such files are encountered by Inkscape users in daily usage).