My issue does appear to be related to a know exiv2 bug. However that bug was supposedly fixed and it appears to me that I have the latest version of exiv2. Does the info below reveal any packaging issue or anything else I should alert the Arch ufraw maintainer or packager about? Thanks (and forgive me if it is not appropriate to continue the conversation here).
Bug #1584853 “Shotwell crashes on startup / Crash in exiv2 due t...” : Bugs : exiv2 package : Ubuntu https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1584853 Bug 765963 – assert in exiv2 when writing metadata https://bugzilla.gnome.org/show_bug.cgi?id=765963 Bug #1106: Crash in exiv2 due to assertion when setting rating on jpg with a Casio makernote - Exiv2 http://dev.exiv2.org/issues/1106 $ uname -a Linux myserver 4.6.4-1-ARCH #1 SMP PREEMPT Mon Jul 11 19:12:32 CEST 2016 x86_64 GNU/Linux $ exiv2 --version exiv2 0.25 001900 (64 bit build) $ ufraw --version ufraw 0.22 EXIV2 enabled. JPEG enabled. JPEG2000 (libjasper) enabled. TIFF enabled. PNG enabled. FITS enabled. ZIP enabled. BZIP2 enabled. LENSFUN enabled. On Mon, Aug 1, 2016 at 1:31 PM, Pascal de Bruijn <pmjdebru...@pcode.nl> wrote: > On Sat, Jul 30, 2016 at 10:37 PM, Dave T <davestechs...@gmail.com> wrote: > >> I'm running Arch Linux 64 bit. I installed this package today: >> >> Arch Linux - gimp-ufraw 0.22-7 (x86_64) >> https://www.archlinux.org/packages/comm … imp-ufraw/ >> <https://www.archlinux.org/packages/community/x86_64/gimp-ufraw/> >> >> install: >> >> $ sudo pacman -S gimp-ufraw >> >> run: >> >> ufraw /path/to/file.dng >> >> Error message: >> >>> ufraw: tiffcomposite.cpp:749: virtual Exiv2::Internal::TiffComponent* >>> Exiv2::Internal::TiffMnEntry::doAddPath(uint16_t, >>> Exiv2::Internal::TiffPath&, Exiv2::Internal::TiffComponent*, >>> Exiv2::Internal::TiffComponent::AutoPtr): Assertion `mn_' failed. >>> Aborted (core dumped) >>> >>> I would guess this is most likely an Exiv2 issue (in which case you'd > need to report the issue there), not per-se UFRaw... but... > > Does archlinux install debug symbols by default? Or do you need to install > ufraw-debug or ufraw-dbg package for that? If need be, please do so... then > try: > > gdb ufraw /path/to/file.dng > r > (do whatever it takes to make it crash) > bt > > and post the backtrace back here. > > Regards, > Pascal de Bruijn > > PS: As a sidenote, what is the source of the DNG file you're trying to > load? Is it straight from a DNG capable camera? Is it a DNG converted from > a RAW using Adobe's DNG Converter? Or is a DNG converter from a RAW using > an atrocious third party DNG converter? And what camera in particular is > the source of the original file? > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > ufraw-devel mailing list > ufraw-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ufraw-devel > >
------------------------------------------------------------------------------
_______________________________________________ ufraw-devel mailing list ufraw-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ufraw-devel
