Bug 283373 - digiKam shows splashscreen but won't start with no crash report generated.
Summary: digiKam shows splashscreen but won't start with no crash report generated.
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: ProgressManager-Splashscreen (show other bugs)
Version: 2.2.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-05 07:22 UTC by Dirk Kesseler
Modified: 2024-05-29 07:23 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.4.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Kesseler 2011-10-05 07:22:57 UTC
Version:           2.2.0 (using KDE 4.7.1) 
OS:                Linux

digikam won't start. No matter how I start digikam, only the splahscreen is shown, nothing more happens! 
Fact: No crash report is genereted. so  I can't give you more detailed infomations! Sorry!

Reproducible: Always

Steps to Reproduce:
1. Tried start up with menu icon: The splashscreen is shown a view seconds. Nothing happens after this.

2. Tried start up via console: The splashscreen is shown a view seconds
Nothing happens after this.

Actual Results:  
Start up detail via conole:

dirk@TUX:~> digikam
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
digikam: symbol lookup error: digikam: undefined symbol: _ZN11KExiv2Iface14AltLangStrEdit15setLinesVisibleEj


Expected Results:  
Nothing happens!

Nothing!
Comment 1 caulier.gilles 2011-10-05 08:03:51 UTC
There is a problem in your computer about libkexiv2 from KDEGraphics component. 

digikam: symbol lookup error: digikam: undefined symbol:
_ZN11KExiv2Iface14AltLangStrEdit15setLinesVisibleEj

binary compatibility is broken between packages. digiKam have been recompiled with another libkexiv2.

Do you have more than one libkexiv2 on your computer ?

Gilles Caulier
Comment 2 Dirk Kesseler 2011-10-05 10:26:18 UTC
(In reply to comment #0)
> Version:           2.2.0 (using KDE 4.7.1) 
> OS:                Linux
> 
> digikam won't start. No matter how I start digikam, only the splahscreen is
> shown, nothing more happens! 
> Fact: No crash report is genereted. so  I can't give you more detailed
> infomations! Sorry!
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. Tried start up with menu icon: The splashscreen is shown a view seconds.
> Nothing happens after this.
> 
> 2. Tried start up via console: The splashscreen is shown a view seconds
> Nothing happens after this.
> 
> Actual Results:  
> Start up detail via conole:
> 
> dirk@TUX:~> digikam
> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
> use, all queries will cease to work.
> digikam: symbol lookup error: digikam: undefined symbol:
> _ZN11KExiv2Iface14AltLangStrEdit15setLinesVisibleEj
> 
> 
> Expected Results:  
> Nothing happens!
> 
> Nothing!

(In reply to comment #1)
> There is a problem in your computer about libkexiv2 from KDEGraphics component. 
> 
> digikam: symbol lookup error: digikam: undefined symbol:
> _ZN11KExiv2Iface14AltLangStrEdit15setLinesVisibleEj
> 
> binary compatibility is broken between packages. digiKam have been recompiled
> with another libkexiv2.
> 
> Do you have more than one libkexiv2 on your computer ?
> 
> Gilles Caulier

(In reply to comment #1)
> There is a problem in your computer about libkexiv2 from KDEGraphics component. 
> 
> digikam: symbol lookup error: digikam: undefined symbol:
> _ZN11KExiv2Iface14AltLangStrEdit15setLinesVisibleEj
> 
> binary compatibility is broken between packages. digiKam have been recompiled
> with another libkexiv2.
> 
> Do you have more than one libkexiv2 on your computer ?
> 
> Gilles Caulier

Hey!
Yes. I found two libkexiv2-installations. The first is "libkexiv2-10" (for KDE 4.7.1)
and the other "libkexiv2-9" (for KDE 4.6.0). I deleted the last one, but nothing happened basicly. The newer one is necessary for KDE 4.7.1!

Dirk
Comment 3 caulier.gilles 2011-10-05 10:28:14 UTC
digiKam and co need to be recompiled to adjust linking properly...

Gilles Caulier
Comment 4 Oliver Wieland 2011-10-08 07:59:03 UTC
Hi!
I can confirm this issue (Kubuntu 11.04, KDE SC 4.7.1, digikam 2.2.0)
There are two versions of libexiv in the ubuntu repositories:

libexiv2-6
libexiv2-10

Both I have installed.

Which version of libexiv2 do I need for digikam 2.2.0?

Regards
Oli
Comment 5 caulier.gilles 2011-10-08 08:05:22 UTC
This depand of package used to compile digiKam. Both are certainly no binary compatible. At least, the last one is always better...

Ask to your distro team for technical details.

Gilles Caulier
Comment 6 Martin Schlander 2011-10-10 19:31:49 UTC
For people having the crash on openSUSE using the _unsupported_ KDE:UpdatedApps repo.

Updated packages are underway. Possibly already available as I write, depending on your architecture.

Make sure you also update libexiv2-11, libkdcraw20 and libkipi8 to the versions provided by the KDE:UpdatedApps repo.

To be sure you have the correct set of packages update using:
'zypper dup --from http://download.opensuse.org/repositories/KDE:/UpdatedApps/openSUSE_11.4/'

These are the packages you should have installed:

cb400f@worKstation:~> rpm -q digikam libexiv2-11 libkdcraw20 libkipi8
digikam-2.2.0-16.1.x86_64
libexiv2-11-0.22-3.1.x86_64
libkdcraw20-4.6.25-500.1.x86_64
libkipi8-4.6.25-500.1.x86_64
cb400f@worKstation:~> 

And please, if you have these types of installation problems with unsupported repositories, ask on the opensuse-kde mailinglist or irc-channel before filing bugreports upstream.
Comment 7 caulier.gilles 2011-11-03 12:42:37 UTC
digiKam 2.2.0 is out since few weeks. Crash still valid with this version ?

Gilles Caulier
Comment 8 caulier.gilles 2011-12-12 18:40:22 UTC
Dirk, Martin,

This entry still valid using 2.4 release ?

Gilles Caulier
Comment 9 Martin Schlander 2011-12-12 18:51:34 UTC
It's not valid with any version of digikam on openSUSE.

It's people with inconsistent installations and often also mixing incompatible repositories.