[digikam] [Bug 375809] New: digiKam froze on opening Settings

classic Classic list List threaded Threaded
26 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 375809] digiKam froze on opening Settings

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

--- Comment #20 from wildcowboy <[hidden email]> ---
Could you follow up, please.
http://dev.exiv2.org/issues/1275#change-5817


(In reply to caulier.gilles from comment #19)
> Thanks
>
> Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 375809] digiKam froze on opening Settings

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375809

--- Comment #21 from [hidden email] ---
WildCowboy,

I already resume how to reproduce the exception in comment #11.
It's possible that crash cannot be reproduced Exiv2 CLI tool if method
explained in comment #11 is not used. Exiv2 team must take a look on my
investigations on this report. I will not re-explain again the details.

There is no need an image to test this crash. In digiKam it's happen when code
extract all avaialble Exiftags with details, descriptions, etc... for the
library database.

Exiv2 tem must write a dedicated unit test code to reproduce this very simple
exception case.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 375809] digiKam froze on opening Settings

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375809

--- Comment #22 from wildcowboy <[hidden email]> ---
Gilles,

Could you help please?
http://dev.exiv2.org/issues/1275#change-5820

(In reply to caulier.gilles from comment #21)

> WildCowboy,
>
> I already resume how to reproduce the exception in comment #11.
> It's possible that crash cannot be reproduced Exiv2 CLI tool if method
> explained in comment #11 is not used. Exiv2 team must take a look on my
> investigations on this report. I will not re-explain again the details.
>
> There is no need an image to test this crash. In digiKam it's happen when
> code extract all avaialble Exiftags with details, descriptions, etc... for
> the library database.
>
> Exiv2 tem must write a dedicated unit test code to reproduce this very
> simple exception case.
>
> Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 375809] digiKam froze on opening Settings

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375809

--- Comment #23 from [hidden email] ---
Git commit 91408e9ece701961beb09461d94b1f6fdaf6a01f by Gilles Caulier.
Committed on 09/02/2017 at 15:57.
Pushed by cgilles into branch 'master'.

Exiv2 0.26-svn commit

http://dev.exiv2.org/projects/exiv2/repository/revisions/4705

fix the MPF Exif group exception

M  +1    -2    libs/dmetadata/metaengine_exif.cpp

https://commits.kde.org/digikam/91408e9ece701961beb09461d94b1f6fdaf6a01f

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 375809] digiKam froze on opening Settings

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375809

--- Comment #24 from Maik Qualmann <[hidden email]> ---
*** Bug 377433 has been marked as a duplicate of this bug. ***

--
You are receiving this mail because:
You are the assignee for the bug.
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 375809] digiKam froze on opening Settings

bugzilla_noreply
In reply to this post by bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375809

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |setup

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