https://bugs.kde.org/show_bug.cgi?id=382174
Simon <freisi...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|UPSTREAM |---
--- Comment #9 from Simon <freisi...@gmail.com> ---
And the ball is back with us. Here is the response by the upstream maintainer:
> [...]
>
> Regardless, this is not a bug in libjpeg-turbo. libjpeg-turbo is printing a
> warning that it encountered a JFIF marker it doesn't understand. The default
> behavior of the library is to continue decoding the image when such a warning
> is encountered. Applications are free to ignore those warnings or to treat
> them as fatal. Both can be accomplished by creating a custom error manager
> using the libjpeg API, and modifications to the TurboJPEG API in dev/1.6
> evolving make it possible to ignore warnings or treat them as fatal in that
> API as well.
>
> Thus, there isn't anything we can do about this. If digiKam is treating the
> warning as fatal, then digiKam needs to be modified. Otherwise, if digiKam is
> continuing to decode the image after the warning, then it's a non-issue.
>
> [...]
--
You are receiving this mail because:
You are watching all bug changes.
