[kde-linux] Re: Digikam and Gwenview cannot find kipi plugins

Duncan 1i5t5.duncan at cox.net
Tue Jul 12 09:01:44 UTC 2011

Bogus Zaba posted on Tue, 12 Jul 2011 08:16:32 +0100 as excerpted:

> Slackware 13.37, KDE 4.5.5 (as supplied by Slackware).

Thanks.  Way too many people don't include even that basic level of info.

> I have both Digikam (1.9) and kipi-plugins (1.9) installed from 
> Slackware packages. Neither digikam nor gwenview can see any plugins. 
> Tried re-installing both digikam and kipi-plugins, but I still have the 
> same outcome - no kipi-plugins available.
> The digikam splash screen provides a few progress messages among which 
> is "loading kipi plugins", but nothing seems to result from this.
> One clue might be this output which comes from running gwenview at the 
> command line:
> "
> gwenview(14654)/kdecore (trader) KServiceTypeTrader::defaultOffers: 
> KServiceTypeTrader: serviceType "KIPI/Plugin" not found
> "
> This suggests that kipi-plugins should have registered itself as a KDE4 
> service (presumably during installation of kipi-plugins). There may be 
> something in my KDE4 setup which is preventing this.
> Any clues as to how I may be able to correct this?

You are very likely correct, as kipi-plugins (here on Gentoo ~amd64 
running the kde overlay) installs these service files:


Try checking your kipi-plugins package to see if it installed them and 

Then try stracing gwenview to see where it's looking for them, with a 
command such as this (-f says follow forks, -eopen says report on file-
open attempts only, 2>&1 redirects STDERR to STDOUT so it can be grepped, 
ENOENT = error, no entry, can't find the file):

strace -feopen gwenview 2>&1 | grep ENOENT

That's still likely to produce a whole slew of output, but you can 
further pipe it to grep -v to remove stuff that looks uninteresting (-v 
reverses the grep, showing only lines that do NOT contain the search 

Eventually you should be able to figure out where it's looking, and 
create symlinks or some such, as necessary (plus file a bug with slack, I 

If the package doesn't include those files at all... well, I guess I 
could try sending a tarball.  They're not huge.  (Mostly they're name and 
comment lines in dozens of different languages, but there's a few real 
operational lines too.  It doesn't appear that they include path or 
version info, so any copy you can find should work, and the symlinks 
should stay working across versions as well, as long as the package 
continues putting them in the same place and the apps continue looking 
for them in the same place.

Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

More information about the kde-linux mailing list