https://bugs.kde.org/show_bug.cgi?id=375952
--- Comment #5 from Matthias Fauconneau <matthias.fauconn...@gmail.com> --- Just noticed, this doesnt look like a segfault but an unhandled exception. It is valid for Exiv2 to abort if it doesnt support APNGs. So it would seem issues are also Gwenview calling Exiv2 on APNGs and not catching the exception (in Exiv2ImageLoader::load or LoadingDocumentImplPrivate::loadMetaInfo), maybe there is a catch further up the (semantic) call chain, but it cannot be unwinded because of the intervening QtConcurrent threading ? On Mon, Feb 6, 2017 at 1:49 PM, Matthias Fauconneau < matthias.fauconn...@gmail.com> wrote: > As a workaround, I disabled PNG support in exiv2. > I wonder why when I open an image, Gwenview tries to load metadata of > another one though. > > On Mon, Feb 6, 2017 at 12:39 PM, Christoph Feck <bugzilla_nore...@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=375952 >> >> Christoph Feck <cf...@kde.org> changed: >> >> What |Removed |Added >> ------------------------------------------------------------ >> ---------------- >> Status|NEEDSINFO |RESOLVED >> Resolution|BACKTRACE |UPSTREAM >> >> --- Comment #3 from Christoph Feck <cf...@kde.org> --- >> The crash is in libexiv2.so.14 >> >> If you know the image that it fails with, please report this issue >> directly to >> libexiv2 developers via http://dev.exiv2.org/projects/exiv2/issues >> >> -- >> You are receiving this mail because: >> You reported the bug. >> > > -- You are receiving this mail because: You are watching all bug changes.
