Arch Linux

snack

Member

From: Italy

Registered: 2009-01-13

Posts: 861

digiKam doesn't start

Hello everyone, I installed digikam from extra, but it doesn't start even if the installation went fine. The error I get is:

$ digikam
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
digikam(3290) Digikam::DigikamFirstRun::DigikamFirstRun: "/home/user"
digikam: symbol lookup error: digikam: undefined symbol: _Z13qFlagLocationPKc

The Xlib error on the first line appears frequently also in other application such as Eclipse, but it doesn't affect their behavior noticeably, so I think the problem is in the last line.
I run KDEmod on Arch i686.

Thanks everyone for the help!

dwende

Member

From: Israel

Registered: 2008-12-04

Posts: 27

Re: digiKam doesn't start

I have exact same problem.

snack

Member

From: Italy

Registered: 2009-01-13

Posts: 861

Re: digiKam doesn't start

I found the problem: I was ignoring the new version of qt (4.5.0-3) and keeping the old 4.4.3-5 because the Lancelot launcher do not display anything when one uses the newest qt. I did the update and digikam started to work flawlessly.
Now, the question marks are:
- why Lancelot doesn't like qt 4.5.0-3? Should I open a bug report?
- is there a good reason why pacman didn't warn me about this dependency problem? I was ignoring the updates of qt due to the Lancelot problem, but in my view pacman should at least give a warning when trying to install a package whose dependencies cannot be resolved due to explicit upgrade ignore.

Rasi

Member

From: Germany

Registered: 2007-08-14

Posts: 1,914

Website

Re: digiKam doesn't start

I found the problem: I was ignoring the new version of qt (4.5.0-3) and keeping the old 4.4.3-5 because the Lancelot launcher do not display anything when one uses the newest qt. I did the update and digikam started to work flawlessly.
Now, the question marks are:
- why Lancelot doesn't like qt 4.5.0-3? Should I open a bug report?
- is there a good reason why pacman didn't warn me about this dependency problem? I was ignoring the updates of qt due to the Lancelot problem, but in my view pacman should at least give a warning when trying to install a package whose dependencies cannot be resolved due to explicit upgrade ignore.

rebuild lancelot? It works fine here using kdemod.

---

He hoped and prayed that there wasn't an afterlife. Then he realized there was a contradiction involved here and merely hoped that there wasn't an afterlife.

Douglas Adams

snack

Member

From: Italy

Registered: 2009-01-13

Posts: 861

Re: digiKam doesn't start

I'll give it  a try, thanks for the advice. But I can live well also without Lancelot (I put kickoff back), so maybe my laziness will win...

test1000

Member

Registered: 2005-04-03

Posts: 834

Re: digiKam doesn't start

alse see: http://wiki.archlinux.org/index.php/Common_Issues

---

KISS = "It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience." - Albert Einstein

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: digiKam doesn't start

- is there a good reason why pacman didn't warn me about this dependency problem? I was ignoring the updates of qt due to the Lancelot problem, but in my view pacman should at least give a warning when trying to install a package whose dependencies cannot be resolved due to explicit upgrade ignore.

There was no problem.
Dependency tree goes like this (roughly): digikam -> kdegraphics/kdepimlibs -> kdelibs -> stuff like phonon/soprano/strigi -> qt
So for pacman, there was no qt dependency involved at all for the digikam upgrade.

Last edited by byte (2009-03-25 13:57:36)

---

1000

snack

Member

From: Italy

Registered: 2009-01-13

Posts: 861

Re: digiKam doesn't start

- is there a good reason why pacman didn't warn me about this dependency problem? I was ignoring the updates of qt due to the Lancelot problem, but in my view pacman should at least give a warning when trying to install a package whose dependencies cannot be resolved due to explicit upgrade ignore.

There was no problem.
Dependency tree goes like this (roughly): digikam -> kdegraphics/kdepimlibs -> kdelibs -> stuff like phonon/soprano/strigi -> qt
So for pacman, there was no qt dependency involved at all for the digikam upgrade.

Thank you, that restores my full trust in pacman (the main, but not only, reason why I prefer Arch over all that *buntu stuff out there... ). But it also means that the rolling release system adopted by Arch is prone to this kind of errors (a very fair trade, in my opinion, since pacman is easily the best package manager I've ever seen).