On Thu, 6 Jan 2022 05:40:37 -0500 Andres Salomon <[email protected]>
wrote:
> On Thu, 06 May 2021 13:05:58 +0300 Henry Jameson wrote:
> > There's a similar bug report in ArchLinux:
> > https://bugs.archlinux.org/task/67105
> >
> > Supposedly they had some custom patch for libpng that was causing
> this and
> > removing that helped. Dunno if debian has anything like this.
> >
> > I can confirm that downloading libpng binary from
> > http://www.libpng.org/pub/png/libpng.html and running chromium
with that
> > library in LD_PRELOAD fixes the issue completely.
> >
> > --
> > Best regards,
> >
> > HJ
> >
> >
> >
>
> >
>
>
> I just looked into it; debian's libpng carries that same patch.
> Specifically, libpng-1.6.37-apng.patch from
> https://sourceforge.net/projects/libpng-apng/files/.
>
> The request for upstream libpng to include the patch is at
> https://sourceforge.net/p/libpng/feature-requests/16/, but upstream
> libpng never merged it. Chromium bundles libpng without that patch,
and
> seems to have made APNGs work without needing to patch libpng. To fix
> this bug, chromium should either use the bundled version of libpng,
or
> debian's libpng should drop libpng-1.6.37-apng.patch.
>
> I'm curious what the libpng maintainers think?
>
The libpng maintainers dropped the broken patch (thanks Gianfranco!),
so this is fixed in bookworm and unstable. Still an issue in bullseye,
but probably not high enough priority to get a point release fix or a
libpng backport.
