Bug 144200

Summary:	Digikam won't display or import thumbnails
Product:	[Applications] digikam	Reporter:	Stan Senuta Jr. <ssenuta>
Component:	Database-Albums	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:	5.7.0
Sentry Crash Report:

Description Stan Senuta Jr. 2007-04-14 07:43:44 UTC

Version:           0,80 (using KDE KDE 3.5.6)
Installed from:    Compiled From Sources
Compiler:          gcc-4.0.1 
OS:                Linux

Digikam won't display or import thumbnails on my system. I can download pictures from the camera but the only way I can be sure the download was successful is to use Digikam's Album menu & open the album in konqueror. 

Here is the error message I get if I try to import an existing album:

	Can't start process. Unable to create io_slave:
	Klauncher said: unknown protocol digikamalbums

I am pretty sure this happens because I have kde-3.5.6 installed in my home directory. If I could find a digikam.rpm file that was relocatable I'd try to install it to ~/home/kde-3.5.6/bin instead of the default /usr/bin. Maybe digikam isn't telling kde-3.5.6 about the digikamalbums protocol because it can't find the new kde. 

Digikam could be telling my inactive kde-3.4.2 in /usr/bin about its digikamalbums protocol instead of the live kde-3.5.6. I'm only guessing here because you would think the digikam installation proceedure would be smart enough to check my KDEDIRS=~/kde-3.5.6 environment entry before it installs.

Also, I discovered that if I create a kde-menu item that starts digikam as a "different" non-root user, thumbnails will be veiwable ...But then that user cannot download files from the usb camera

Comment 1 Stan Senuta Jr. 2007-04-14 07:57:11 UTC

Digikam was installed from a .rpm file.   Kde-3.5.6 was installed via src tarballs. 

Digikam worked just fine under my kde-3.4.2 which is still located in my /usr directory.

Comment 2 caulier.gilles 2007-04-14 08:19:10 UTC

Stan,

First, the installation of digiKam KIO slaves are broken in your system (problably installed on the wrong folder).

Second, digiKam 0.8.0 is too old. Please update to 0.9.1.

Gilles Caulier

Comment 3 Stan Senuta Jr. 2007-04-14 21:06:01 UTC

Should there be a listing for a Digikam kio_slave in Kinfocenter under Protocols.?  

Where does the "slave" get installed & is this kio_slave installed by a 
KDE pkg or the Digikam pkg.?

I'm wondering if the missing kio_slave is in the kde-3.5.6 "kdeaddons tarball".
I never compiled that one.

Isn't the purpose kio-slaves to enable KDE to find "remote" files & treat them like local files? If so, then why can't the digikamalbums protocol be found.? It has got to be on my system somewhere. 

By-the-way, I did try to compile Digikam from a tarball hoping to use the ./configure --prefix= option to relocate it to ~/home/kde-3.5.6/bin, but
it failed to compile. 

Thanks for you quick response. I appreciate you paying attention to guys like me who have Kde installed in non-standard locations. ---stan

Comment 4 caulier.gilles 2017-07-23 20:46:54 UTC

This problem is relevant of digiKam KIO slaves which are dropped since version 5.0.0 in favor of a multithreaded interface to query the database. It will not reproducible.