https://bugs.kde.org/show_bug.cgi?id=391039
--- Comment #8 from caulier.gil...@gmail.com ---
Strange, i cannot reproduce the problem here. I process panorama many time by
month without to notice this kind of dysfunction.
Please instead to try a fresh release, if you can try with same release than me
as 2016.2 which work like a charm here (official package from Mageia6)
Note: i remember that i report a dysfunction in Magiea team about hugin, linked
with a bugous version of Exiv2 (0.25) which stop the processing quickly without
any report in digiKam. I discovered the source of the problem by running Hugin
CLI tool by hand on my image and finally to seen an Exiv2 crash while metadata
parsing.
The reason to not seen any report in digiKam is the way to process Hugin stage
in separated and chained threads. Probably a missing exception catch can fix
the problem but in all case, using Exiv2 0.26 so far more safe than 0.25.
To be sure, run ldd over the hugin executable and look which Exiv2 version is
used at linking time. Mine :
[gilles@localhost reports]$ ldd /usr/bin/hugin |grep exiv2
libexiv2.so.26 => /lib64/libexiv2.so.26 (0x00007f5c4dc0e000)
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
