FS#28124 - [digikam] symbol lookup error - probably linked against wrong libkgeomap version

Attached to Project: Arch Linux
Opened by Sam (smls) - Friday, 27 January 2012, 09:42 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 27 January 2012, 14:58 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

The current version of digiKam fails to show any pictures - all albums appear empty.
Console output and log-file claim an error trying to start the "kio_digikamalbums" io-slave, due to an undefined symbol "[...]MarbleWidget[...]" in /usr/lib/libkgeomap.so.1 (owned by libkgeomap).

The bug has been reported in KDE's bug tracker by a Ubuntu user, where the developers came to the conclusion that it was a distro packaging issue, noting that every minor release of the Marble widget requires a recompile of digiKam against it.

Additional info:

* package versions:

- digikam 2.5.0-1
- libkgeomap 2.5.0-1

* upstream bug report:

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

* excerpt from console output when staring digiKam from console:

digikam(25649): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_digikamalbums'.

* excerpt from ~/.xsession-errors:

Could not open library '/usr/lib/kde4/kio_digikamalbums.so'.
Cannot load library /usr/lib/kde4/kio_digikamalbums.so: (/usr/lib/libkgeomap.so.1: undefined symbol: _ZN6Marble12MarbleWidget14geoCoordinatesEiiRdS1_NS_18GeoDataCoordinates4UnitE)
digikam(20356): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_digikamalbums'.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Friday, 27 January 2012, 14:58 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#28127 
Comment by Sam (smls) - Friday, 27 January 2012, 14:51 GMT
Ok, I think this bug report of mine can be discarded...

I mistakenly assumed that the issue was confined to only the digikam and libkgeomap packages, which are both from extra, and therefore should be expected to work together, leading me to think it was a packaging bug.

But in fact the root of the problem seems to be that I have kdeedu-marble from [testing] installed, which provides libmarblewidget.so.13 instead of the libmarblewidget.so.12 which libkgeomap from [extra] is linked against, which in turn digikam from [extra] is linked against.

I had already earlier, for a different reason, symlinked /usr/lib/libmarblewidget.so.12 -> /usr/lib/libmarblewidget.so.13, causing digikam to start but exhibit the strange situation described above.

So this is in fact a duplicate of: https://bugs.archlinux.org/task/28127

Sorry for the noise...

Loading...