Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Mar 2018 22:24:52 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 226544] ufraw crashes loading ufraw file with image made with "unknown" camera info
Message-ID:  <bug-226544-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226544

            Bug ID: 226544
           Summary: ufraw crashes loading ufraw file with image made with
                    "unknown" camera info
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: freebsd@dreamchaser.org

If an image made with a camera which does not exist in the lensfun database=
 is
loaded and the camera is set to the closest match
  (e.g. image taken with Olympus E-M1 MarkII, camera set in ufraw to "Olymp=
us,
E-M1)
ufraw writes the CameraModel to the .ufraw file:
  <CameraModel>Olympus, E-M1</CameraModel>
in the <LensFun> section.
Ufraw will correctly load from this ufraw file.

However, when it loads, no potential lens information is present in the
dropdown.
If one then manually resets the camera model to the same model shown, the
potential lens info is shown.
If a new ufraw file is now written, it will contain the lens information bu=
t no
camera information.  Attempting to load this file will cause ufraw to crash.
Adding any camera information manually to the .ufraw file will also cause u=
fraw
to crash, whether the camera is in the database or not, apparently because =
the
camera does not match the one given in the loaded image.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226544-13>