Jaunty ships with libraries too old for digikam-kde4

Bug #384278 reported by Tony Green
8
This bug affects 2 people
Affects Status Importance Assigned to Milestone
digikam (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: digikam

I have reported a bug (https://bugs.kde.org/show_bug.cgi?id=195448) with KDE for Digikam 0.10.0 crashing fatally (and taking the whole computer out!)
From the diagnostics I supplied, the developer (Gilles Caulier) has deduced that a number of libraries installed in Jaunty are actually too old for the KDE4 version of Digikam and could be the source of my problem.

Specifically (quoting Gilles)
---------------------------------------------------------------------------------------------------
LibExiv2: 0.18 [currently installed version]

==> i recommend to use last Exiv2 0.18.1, to be sure...

LibKdcraw: 0.4.2 [currently installed version]

=> A little bit old. this is the lead RAW interface for digiKam.

LibRaw: 0.6.15-Release [currently installed version]

This one is the MUST important. it's integrated into libkdcraw as well (no
external package) .this is the core component to handle RAW in all ways.

With current code of libkdcraw (integrated with KDE/Kdegraphics component,
libraw version is 0.7.2. I recomment to take a look to update it.
-------------------------------------------------------------------------------------------
I have searched around for newer versions of these to install with no success. So it seems that Jaunty is probably (assuming I haven't missed something obvious) shipping with out-of-date libraries required by Digikam's KDE4 release.

This is a pretty serious problem as it leads to the computer completely hanging up during the import of RAW image files into Digikam - nothing but a hard reset brings it back.

Details:
Release is Kubuntu 9.04, AMD-64 architecture
Digikam version is 0.10.0

Revision history for this message
Harald Sitter (apachelogger) wrote :

Well, yeah, no.

libkdcraw got different API and ABI versions, API versions 0.4.2 is really ABI version 7.0.0 (that is what we got in Jaunty). obviously digikam only spits out the API version with no regards to the ABI, and what Gilles calls 0.7.2 is really 0.4.2, since there never was a 0.7.2 (KDE 4.2.0 came with 0.4.2/7.0.0, and KDE got a no-API-no-ABI breakage policy, so 0.4.2/7.0.0 will be carried throughout KDE 4.2 ... KDE 4.3 on the other hand will be 0.5.0/7.1.0)

Also, if I am not mistaken we don't link libkdcraw nor digikam against an independent libraw (i.e. another one than the one in kdegraphics), so there is no way you can update either of them due to the no-API-no-ABI-breakage policy from KDE mentioned earlier. Well, you would need to update to KDE trunk or KDE 4.3 beta, which then again means rebuild digikam ... so this hardly can be the solution here.

So really, we can't do anything about it, so would no other distribution (which by the way should be affected as well, because we don't apply any patches on lib(kdc)raw), so unless Gilles is wrong and the crash is not happening in libraw itself, the issue remains very annoying and awful, but unfixable (at least untill someone can proof that this issue is really in libraw and find out how to fix it). Otherwise it should autoresolve with an upgrade to KDE 4.3.

I recommend you bounce back to Gilles for now :) The bug will be marked invalid, but really only because we don't have enough information to track the crash location nor to fix it at this point. Please reopen the bug report if you get further information or when you and Gilles should fail to trace the issue any further, we'll then take another look at it.

Changed in digikam (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.