digikam4 does not display images or thumnails in kde4

[Geoff123]

Sometimes (maybe 40% of the time) I can start digikam4 in ubuntu and have it work correctly. When it does not work correctly the problem is that I cannot see thumbnails in the main view and get messages like this on the terminal: digikam(20525): couldn't create slave: "Unable to create io-slave: klauncher said: Unknown protocol 'digikamalbums'.

On ubuntu I have found the way to fix this is to run this command and then restart the digikam script:
"killall klauncher && killall kdeinit4 && killall kded4"

This was initially reported here at http://bugs.kde.org/show_bug.cgi?id=165885

I'm using Ubuntu 8.10 with the gnome desktop with all updates.
I have also tried it on the kde4 desktop, but the situation is worse. In this case it almost never starts correctly, but the killall commands cause other problems.
The digikam4 is the latest SVN of exiv2, libs, digikam.

I have no clue whether this is due to my startup/compile script, digikam4, or kde.
The script I use sets several environment variables, one which is below..
------------
#!/bin/bash
DIGIKAMKDE4=/home/gsking/programs/src/svn/digikam4/build
export KDEDIR=$DIGIKAMKDE4:/usr/lib/kde4
export KDEDIRS=$DIGIKAMKDE4:/usr/lib/kde4
export QTDIR=/usr/lib/qt4
export PATH=$DIGIKAMKDE4/bin:/usr/local/bin:$QTDIR/bin:$KDEDIR/bin:$QTDIR/bin:/usr/local/bin:$PATH
/kde4/libexec:$LD_LIBRARY_PATH
digikam
-------------

[dotancohen (dotancohen)]

By Digikam4 do you mean one of the Digikam 0.10 betas, which are Qt4 based? Or are you using Digikam 0.9.x?

By which method did you install Digikam?

[Geoff123 (gsking1)]

Yes this is the Digikam 0.10.0-beta6 from SVN.
The kipi-plugins and kdegraphics libs are also from SVN and include libkipi, libkdcraw, etc.
Exiv2 is also from SVN.

I should note that when it does start (after using killall) it works great.

[ted (m-v-)]

after following these instructions it actually works great http://wiki.kde.org/tiki-index.php?page=Digikam+Compilation+on+Kubuntu+Intrepid

[Geoff123 (gsking1)]

I just tried and it does work if I install it to a system location (/usr) like the instructions say.
However, I cannot install to a personal directory like the first line of my script example above shows (note this is not the full script, just a partial example).
I still think there is something strange going on. I think all the variables are correct? Why can't I install to a private directory?
Thanks, Geoff

[Steve Langasek (vorlon)]

Thank you for taking the time to report this bug and help to improve Ubuntu.

digikam 0.10.0~rc1 is present in jaunty, and my understanding is that the problems you're having are a result of trying to install digikam from source, rather than due to any defect in the Ubuntu system. I'm therefore closing this bug as 'invalid'.

[Jet (poekie)]

I have this problem too after updating from Intrepid to Jaunty today. I updated using the update manager, so I didn't compile from source and used the (k)ubuntu repositories.

digikam(31006): couldn't create slave: "Unable to create io-slave:
klauncher said: Unknown protocol 'digikamalbums'.

[José Tomás Atria (jtatria)]

i am experiencing this bug on jaunty, kde 4.2, with digikam complaining about the missing kio slaves, and also in kde 4.3 beta 2 (4.2.90), without any mention about kio slaves.

all installations were performed through apt, with kubuntu repos.

in other words, i haven't been able to use digikam in any version of kubuntu with the currently packaged repos.

[José Tomás Atria (jtatria)]

the bug persists in kde 4.3 RC3 (4.2.98), and i see there's no movement at all here. bummer.

[Dhaval Patel (dhuv)]

I am also seeing the same problem with Jaunty and latest updates to KDE 4.3. I am happy to try things and send back information if anyone has suggestions.

[Luka Renko (lure)]

Can you try latest digikam 1.0.0 beta5 from backports PPA?
https://launchpad.net/~kubuntu-ppa/+archive/backports

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!