[digikam] [Bug 366034] New: Crash at edit metadata for jpgs made by a Casio EX-Z500

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366034

            Bug ID: 366034
           Summary: Crash at edit metadata for jpgs made by a Casio
                    EX-Z500
           Product: digikam
           Version: 5.0.0
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: Metadata-Editor
          Assignee: [hidden email]
          Reporter: [hidden email]

Created attachment 100266
  --> https://bugs.kde.org/attachment.cgi?id=100266&action=edit
Image that leads to the crash

Select a jpg made by a Casio Exilim Z500 camera (see the attached image as an
example) and try to edit metadata (Menu Item->Edit Metadata...). digikam shows
a runtime error popup and exits.

Similar behavior in version 4.12.0. Reason for the crash is an memory access
violation according to v4.12.0 error popup.

One example is attached but the crash happens with all images that were made
with this camera.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366034

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
             Status|UNCONFIRMED                 |RESOLVED
          Component|Metadata-Editor             |Metadata-Engine
         Resolution|---                         |UPSTREAM

--- Comment #1 from [hidden email] ---
It's probably due to  crash inside Exiv2 shared library. Metadata Editor read
information in image trough this shared library.

Please report this problem to Exiv2 team with your suspected image for
investigations.

http://dev.exiv2.org/projects/exiv2/issues

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366034

--- Comment #2 from Wolfram Kroiss <[hidden email]> ---
No problems with manipulating these files using exiv2.exe (v0.25) though.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366034

--- Comment #3 from Wolfram Kroiss <[hidden email]> ---
(In reply to caulier.gilles from comment #1)
> It's probably due to  crash inside Exiv2 shared library. Metadata Editor
> read information in image trough this shared library.
>
> Please report this problem to Exiv2 team with your suspected image for
> investigations.
>
> http://dev.exiv2.org/projects/exiv2/issues
>
> Gilles Caulier

Thanks for the hint. This problem seems to be known at exiv2 and a fix is going
to be released with version 0.26 which is due end of July 2016 (in a week from
now).

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel