Problems with compiled Digikam: can't create io-slaves

[Jenner Fusari]

Hi,
I'm another Debian Testing user which has managed to have Digikam back in
his system.
I decided to compile Digikam 4.13 from source using the official tarball. I
ended up with Digikam (apparently) successfully compiled and I made a .deb
package using checkinstall instead of the make install statement.

But here's the problem: Digikam loads fine and seems to work but no image
thumbnail is shown... every time I choose an album I get the following
message in the console:
digikam(7594): couldn't create slave: "Unable to create io-slave: klauncher
said: Unknown protocol 'digikamalbums'."
digikam(7594)/digikam (core) Digikam::ImageAlbumModel::slotResult: Failed to
list url:  "Could not start process Unable to create io-slave: klauncher
said: Unknown protocol 'digikamalbums'."

When I select a tag I get a similar message related to digikamtags:
digikam(7594): couldn't create slave: "Unable to create io-slave: klauncher
said: Unknown protocol 'digikamtags'."
digikam(7594)/digikam (core) Digikam::ImageAlbumModel::slotResult: Failed to
list url:  "Could not start process Unable to create io-slave: klauncher
said: Unknown protocol 'digikamtags'."

So my question is: what's wrong with my compiled version of Digikam? And how
can I fix this problems?

On my system runs a Debian Testing (stretch) on amd64 architecture, LXDE as
desktop manager. Repositories from unstable (sid) and experimental are enabled.

The Debian binary package from unstable won't install (and that's known)
neither compiles using apt-get build-dep / apt-get source (got problems with
Marbles).

Thanks in advance

Bye
   Jenner

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Hi,

It's not a compiling problem, but an install one. The digiKam KIOSLaves are not at the right place on your system. KIOSlaves are separated programs/Process used to query the Database in safe way in case on concurrent requests. There are started by digiKam through KDE run time.

A lots of problems relevant of KIOSLaves have been reported in this room : binary compatibility, install, run-time, portability, etc... With next 5.0.0, the game is over for KIOSLaves : we use multithread/Multicore solution instead now.

So, please look in this mailing list archive for a solution...

Best

Gilles Caulier

2015-10-14 20:49 GMT+02:00 Jenner Fusari <[hidden email]>:

Hi,
I'm another Debian Testing user which has managed to have Digikam back in
his system.
I decided to compile Digikam 4.13 from source using the official tarball. I
ended up with Digikam (apparently) successfully compiled and I made a .deb
package using checkinstall instead of the make install statement.

But here's the problem: Digikam loads fine and seems to work but no image
thumbnail is shown... every time I choose an album I get the following
message in the console:
digikam(7594): couldn't create slave: "Unable to create io-slave: klauncher
said: Unknown protocol 'digikamalbums'."
digikam(7594)/digikam (core) Digikam::ImageAlbumModel::slotResult: Failed to
list url:  "Could not start process Unable to create io-slave: klauncher
said: Unknown protocol 'digikamalbums'."

When I select a tag I get a similar message related to digikamtags:
digikam(7594): couldn't create slave: "Unable to create io-slave: klauncher
said: Unknown protocol 'digikamtags'."
digikam(7594)/digikam (core) Digikam::ImageAlbumModel::slotResult: Failed to
list url:  "Could not start process Unable to create io-slave: klauncher
said: Unknown protocol 'digikamtags'."

So my question is: what's wrong with my compiled version of Digikam? And how
can I fix this problems?

On my system runs a Debian Testing (stretch) on amd64 architecture, LXDE as
desktop manager. Repositories from unstable (sid) and experimental are enabled.

The Debian binary package from unstable won't install (and that's known)
neither compiles using apt-get build-dep / apt-get source (got problems with
Marbles).

Thanks in advance

Bye
   Jenner

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jenner Fusari]

Thank you Gilles, I fixed my Digikam!
Thank to your magic keyword ("KIOSlaves") I could find an old discussion
where is said that Digikam should be in the same KDE path (probed with
kde4-config --prefix ).

How I fixed it: I went in the directory where I have compiled Digikam; I
removed CMakeCache.txt and issued the command:
cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix`
After that I rebuilt the .deb package using checkinstall and all went well! :)

I wasn't aware of KIOSlaves issues (I did the wrong searches... I searched a
lot before posting) cause I focalize on compiling problems. Also I'm not a
KDE user (my KDE experience starts and ends with Digikam) so it'a a pretty
obscure environment for me.

Thank again Gilles. :D

Bye
   Jenner



_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Pedro Neves]

Hi Jenner:

Any change of sharing some info on how to compile Digikam on Debian and
build the package? Is it hard?

Cheers:

Pedro

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Jenner Fusari]

Pedro Neves <nevesdiver@...> writes:
> Any change of sharing some info on how to compile Digikam on Debian and
> build the package? Is it hard?

No, it's quite easy if it's not the first time you compile something on linux.
You have to download the official Digikam tarball first and follow the
instruction in the Digikam README. Refer to the README even for dependencies
because it's more precise and detailed.

Many of the dependencies are already packaged. In the latest Debian Testing
environment you should not find Boost libraries: you have to download and
compile them first (you'll find the urls in the README).
Again, even for Boost, follow the enclosed instruction to compile the libraries.

After installing all the required dependencied you're ready to compile
Digikam... it will take some time and the output is almost unreadable.

I strongly suggest to use checkinstall (you should install it... it's
packaged, so no problem at all). checkinstall replace the "make install"
statement... it's function is to monitor where the "make install" places the
files, collect them and build a stand-alone .deb package. Note that the
packeg you'll get has no dependency in it so it's useful only for system
maintenance purpose.

Hope this helps.

Bye
   Jenner


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users