This is not a digikam bug but a packaging issue. So please report it to opensuse-kde@opensuse.org mailinglist.

It could be that you have to install the sharedlibs package from that repo when using KDE 4.6. If there is none that would be apackaging issue as well.

The local shared library libdigikamcore.so or libdigikamdatabase.so are not the right versions installed to your computer. It's typically a packaging problem.

Gilles Caulier

No idea if it is applicable here but on kubuntu seen a problem, looking like this, been solved by this solution:
Try forcing version downgrade for libkipi from 4.6.5 to 4.6.2 (Philip
Johnsson's PPA) in Synaptic



Op 10-10-11 16:09, Heart schreef:
> https://bugs.kde.org/show_bug.cgi?id=283708
>
>             Summary: digikam don't start after update to package 2.2.0-14.2
>                      (undefined symbol:
>                      _ZN4KIPI21ImageCollectionSharedD2Ev)
>             Product: digikam
>             Version: 2.2.0
>            Platform: openSUSE RPMs
>          OS/Version: Linux
>              Status: UNCONFIRMED
>            Severity: normal
>            Priority: NOR
>           Component: general
>          AssignedTo: digikam-devel@kde.org
>          ReportedBy: heart1010@gmail.com
>
>
> Version:           2.2.0 (using KDE 4.6.0)
> OS:                Linux
>
> After the update from KDE:UpdatedApps Repo (openSUSE 11.4) digikam won't start
> anymore
>
> ~>  digikam
> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
> use, all queries will cease to work.
> digikam: symbol lookup error: digikam: undefined symbol:
> _ZN4KIPI21ImageCollectionSharedD2Ev
>
>
> # zypper se -si digikam kipi
> Daten des Repositorys laden ...
> Installierte Pakete lesen ...
>
> S | Name                      | Typ   | Version      | Arch   | Repository
> --+---------------------------+-------+--------------+--------+-----------------------------------
> i | digikam                   | Paket | 2.2.0-14.2   | i586   | KDE:UpdatedApps
> i | digikam-doc               | Paket | 2.2.0-14.2   | noarch | KDE:UpdatedApps
> i | digikam-lang              | Paket | 2.2.0-14.2   | noarch | KDE:UpdatedApps
> i | kipi-plugins              | Paket | 2.2.0-13.1   | i586   | KDE:UpdatedApps
> i | kipi-plugins-acquireimage | Paket | 2.2.0-13.1   | i586   | KDE:UpdatedApps
> i | kipi-plugins-geolocation  | Paket | 2.2.0-13.1   | i586   | KDE:UpdatedApps
> i | kipi-plugins-lang         | Paket | 2.2.0-13.1   | noarch | KDE:UpdatedApps
> i | libkipi8                  | Paket | 4.6.0-6.11.1 | i586   |
> Aktualisierungen für openSUSE 11.4
>
>
> # kde4-config --version
> Qt: 4.7.1
> KDE: 4.6.00 (4.6.0) "release 6"
> kde4-config: 1.0
>
>
> Reproducible: Always
>
> Steps to Reproduce:
> simply start "digikam"
>
>
> Expected Results:
> ...digikam should start ;)
>
> Many others have reported the same bug/crash here
> http://www.linux-club.de/viewtopic.php?f=12&t=114472&p=718933#p718933
>

Oh mamma mia, again double, I am deeply ashamed and very sorry.
Rinus

Ok, ignored that gwenview dependencies and have now

# zypper se -si digikam kipi
S | Name                      | Typ   | Version      | Arch   | Repository    
--+---------------------------+-------+--------------+--------+----------------
i | digikam                   | Paket | 2.2.0-16.1   | i586   | KDE:UpdatedApps
i | digikam-doc               | Paket | 2.2.0-16.1   | noarch | KDE:UpdatedApps
i | digikam-lang              | Paket | 2.2.0-16.1   | noarch | KDE:UpdatedApps
i | kipi-plugins              | Paket | 2.2.0-13.1   | i586   | KDE:UpdatedApps
i | kipi-plugins-acquireimage | Paket | 2.2.0-13.1   | i586   | KDE:UpdatedApps
i | kipi-plugins-geolocation  | Paket | 2.2.0-13.1   | i586   | KDE:UpdatedApps
i | kipi-plugins-lang         | Paket | 2.2.0-13.1   | noarch | KDE:UpdatedApps
i | libkipi8                  | Paket | 4.6.25-500.1 | i586   | KDE:UpdatedApps

and digikam works again...

THANKS!!

Just in case others find this bug. Some hints:

On openSUSE do not mix KDE:UpdatedApps (KUA) with any KDE:Release:xy (KRxy) repo.

Disable KUA when using KRxy as it is meant for plain 11.4 only, same for Extra!

After you have added a KRxy repo use zypper dup --from <name-of-KRxy-repo> or in YaST, at the top of the packages list when selecting the KRxy repo, "switch packages…" to use all packages from that new repo.