Created attachment 640301 [details]
Crash information

Hi, this is an old issue but still alive.

Development of Digikam has been very active and has included many features
together with bug solving. The default Digikam version has been left way behind
this process. However, more recent versions of Digikam can be found in
KDE:EXTRA repo.
The problem is that even the most recent Digikam 4.11, requires a version of
libkexiv2-11 who still requires to have the file libexiv2.so.13 provided by
libexiv2-13 (v.0.24 with the bugs we know about MP4 files among others).

exiv2 has implemented many bug fixes and features having v0.25 available since
long time. However, we still find libkexiv2 being built against libexiv2-13
(with the old and buggy version 0.24) even on the most recent libkexiv2
versions.

The package issue is critical to be solved because anybody upgrading with
KDE:EXTRA, had his/her Digikam killed since a couple of days after upgrading to
DK 4.11.0 despite the wrong dependency of libkexiv2 to libexiv2-13 instead of
libexiv2-14. Among the many bugs of libexiv2.so.13 (exiv2 0.24) there are
problems with MP4 files. These were solved in exiv2 0.25 implemented by
libexiv2.so.14 (provided by libexiv2-14), but even the most recent version of
libkexiv2 has not been built against libexiv2-14. Then if the user has MP4
files within the collections managed by Digikam, among other known issues, it
crashes at start-up every time. As Digikam, there are several other KDE apps
using the buggy version libexiv2-13 instead of libexiv2-14.

Most recent libkexiv2 (15.04.3) that I could find, is distributed by 
KDE:Applications repo and libexiv2-14 by "Graphics" among other repos.

It seems to me that the fastest packaging and distribution solution would be to
have a version of libkexiv2 built against libexiv2-14 and posted in KDE:Extra
since it is where recent Digikam versions are posted as well. Then the three
correct packages could finally met in a single repo.

Thanks in advance
gps