[Digikam-devel] Install in /home borked - what did I do wrong?

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[Digikam-devel] Install in /home borked - what did I do wrong?

Sebastian Roeder
I like it very much to compile/install digikam TRUNK SVN inside my /home dir
cause this makes it impossible to damage the system (make install is not done
as root). However after my complete reinstall of my linux system this doesn't
work anymore. I get the following:

digikam: ScanLib: Finding non-existing Albums: 4 ms
digikam: ScanLib: Finding items not in the database or disk: 261 ms
digikam: ScanLib: Updating items without date: 0 ms
digikam: Cannot parse EXIF metadata using Exiv2
kio (KMimeType): WARNING: KServiceType::offers : servicetype KIPI/Plugin not
found
kio (KMimeType): WARNING: KServiceType::offers : servicetype
Digikam/ImagePlugin  not found
digikam: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unbekanntes Protokoll "digikamdates".
digikam: digikam: WARNING: [void Digikam::AlbumManager::slotResult(KIO::Job*)]
Failed to list dates
digikam: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unbekanntes Protokoll "digikamalbums".
digikam: digikam: WARNING: Failed to list url: Could not start process Unable
to create io-slave:
klauncher said: Unbekanntes Protokoll "digikamalbums".

The difference to the previous install is that libkipi, libkexif etc. are NOT
installed globally but only in /home as well. Looks like they are not found
and I have to adjust some path environmet settings again.

Here is my "startsript" that doesn't work anymore (you see I have tested
different settings allready). The settings that are currently active are from
the ML posted by Joern.

#!/bin/bash

# A little wrapper script to start the latest digikam testbuild
add_root=/home/sero/kde_svn/testbuilds/digikam_trunk
#export KDEDIRS=$add_root
#export KDEDIRS=/home/sero/kde_svn/testbuilds/digikam_trunk:/usr/kde/3.5
#export LD_LIBRARY_PATH=$add_root/lib
#export PATH=$add_root/bin

export KDEDIRS=$add_root:
export PATH=$add_root/bin:$PATH
export LD_LIBRARY_PATH=$add_root/lib
$add_root/bin/digikam

Any help would be much apprecheated.
Thanks in advance!

Sero
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] Install in /home borked - what did I do wrong?

Gilles Caulier-2
On Tuesday 25 April 2006 12:22 pm, Sebastian Röder wrote:

> I like it very much to compile/install digikam TRUNK SVN inside my /home
> dir cause this makes it impossible to damage the system (make install is
> not done as root). However after my complete reinstall of my linux system
> this doesn't work anymore. I get the following:
>
> digikam: ScanLib: Finding non-existing Albums: 4 ms
> digikam: ScanLib: Finding items not in the database or disk: 261 ms
> digikam: ScanLib: Updating items without date: 0 ms
> digikam: Cannot parse EXIF metadata using Exiv2
> kio (KMimeType): WARNING: KServiceType::offers : servicetype KIPI/Plugin
> not found
> kio (KMimeType): WARNING: KServiceType::offers : servicetype
> Digikam/ImagePlugin  not found
> digikam: ERROR: : couldn't create slave : Unable to create io-slave:
> klauncher said: Unbekanntes Protokoll "digikamdates".
> digikam: digikam: WARNING: [void
> Digikam::AlbumManager::slotResult(KIO::Job*)] Failed to list dates
> digikam: ERROR: : couldn't create slave : Unable to create io-slave:
> klauncher said: Unbekanntes Protokoll "digikamalbums".
> digikam: digikam: WARNING: Failed to list url: Could not start process
> Unable to create io-slave:
> klauncher said: Unbekanntes Protokoll "digikamalbums".
>
> The difference to the previous install is that libkipi, libkexif etc. are
> NOT installed globally but only in /home as well. Looks like they are not
> found and I have to adjust some path environmet settings again.
>
> Here is my "startsript" that doesn't work anymore (you see I have tested
> different settings allready). The settings that are currently active are
> from the ML posted by Joern.
>
> #!/bin/bash
>
> # A little wrapper script to start the latest digikam testbuild
> add_root=/home/sero/kde_svn/testbuilds/digikam_trunk
> #export KDEDIRS=$add_root
> #export KDEDIRS=/home/sero/kde_svn/testbuilds/digikam_trunk:/usr/kde/3.5
> #export LD_LIBRARY_PATH=$add_root/lib
> #export PATH=$add_root/bin
>
> export KDEDIRS=$add_root:
> export PATH=$add_root/bin:$PATH
> export LD_LIBRARY_PATH=$add_root/lib
> $add_root/bin/digikam
>
> Any help would be much apprecheated.
> Thanks in advance!
>

I suspect a wrong install. Have you used .configure --prefix=myhomepath ?

What 'locate libdigikam.la kio_digikamtags.so' done on your computer ?

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] Install in /home borked - what did I do wrong?

Sebastian Roeder
In reply to this post by Sebastian Roeder
Am Dienstag, 25. April 2006 13:36 schrieb [hidden email]:

> > I like it very much to compile/install digikam TRUNK SVN inside my /home
> > dir cause this makes it impossible to damage the system (make install is
> > not done as root). However after my complete reinstall of my linux system
> > this doesn't work anymore. I get the following:
> >
> > kio (KMimeType): WARNING: KServiceType::offers : servicetype KIPI/Plugin
> > not found
> > kio (KMimeType): WARNING: KServiceType::offers : servicetype
> > Digikam/ImagePlugin  not found
> > digikam: ERROR: : couldn't create slave : Unable to create io-slave:
> > klauncher said: Unbekanntes Protokoll "digikamdates".
> > digikam: digikam: WARNING: [void
> > Digikam::AlbumManager::slotResult(KIO::Job*)] Failed to list dates
> > digikam: ERROR: : couldn't create slave : Unable to create io-slave:
> > klauncher said: Unbekanntes Protokoll "digikamalbums".
> > #!/bin/bash
> >
> > # A little wrapper script to start the latest digikam testbuild
> > add_root=/home/sero/kde_svn/testbuilds/digikam_trunk
> > #export KDEDIRS=$add_root
> > #export KDEDIRS=/home/sero/kde_svn/testbuilds/digikam_trunk:/usr/kde/3.5
> > #export LD_LIBRARY_PATH=$add_root/lib
> > #export PATH=$add_root/bin
> >
> > export KDEDIRS=$add_root:
> > export PATH=$add_root/bin:$PATH
> > export LD_LIBRARY_PATH=$add_root/lib
> > $add_root/bin/digikam
> >
> > Any help would be much apprecheated.
> > Thanks in advance!
>
> I suspect a wrong install. Have you used .configure --prefix=myhomepath ?

Yes I did. A wrong install is very unlikely the problem cause I first tried it
with a copy of my last working install and then with a fresh install - both
have the same problem.

> What 'locate libdigikam.la kio_digikamtags.so' done on your computer ?

# locate libdigikam.la
/home/sero/kde_svn/testbuilds/digikam_trunk-0424/lib/libdigikam.la

This is fine cause I have a symlink digikam_trunk --> digikam_trunk-0424

# locate kio_digikam.so

Upps: NOTHING! Where does this belong to? OK, I will do a fresh install again!

Thanks Gilles. Hope this fixes my problem.

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] Install in /home borked - what did I do wrong?

Gilles Caulier-2
On Tuesday 25 April 2006 03:21 pm, Sebastian Röder wrote:

> Am Dienstag, 25. April 2006 13:36 schrieb [hidden email]:> >
> I like it very much to compile/install digikam TRUNK SVN inside my /home> >
> dir cause this makes it impossible to damage the system (make install is> >
> not done as root). However after my complete reinstall of my linux system>
> > this doesn't work anymore. I get the following:> >> > kio (KMimeType):
> WARNING: KServiceType::offers : servicetype KIPI/Plugin> > not found> > kio
> (KMimeType): WARNING: KServiceType::offers : servicetype> >
> Digikam/ImagePlugin  not found> > digikam: ERROR: : couldn't create slave :
> Unable to create io-slave:> > klauncher said: Unbekanntes Protokoll
> "digikamdates".> > digikam: digikam: WARNING: [void> >
> Digikam::AlbumManager::slotResult(KIO::Job*)] Failed to list dates> >
> digikam: ERROR: : couldn't create slave : Unable to create io-slave:> >
> klauncher said: Unbekanntes Protokoll "digikamalbums".> > #!/bin/bash> >> >
> # A little wrapper script to start the latest digikam testbuild> >
> add_root=/home/sero/kde_svn/testbuilds/digikam_trunk> > #export
> KDEDIRS=$add_root> > #export
> KDEDIRS=/home/sero/kde_svn/testbuilds/digikam_trunk:/usr/kde/3.5> > #export
> LD_LIBRARY_PATH=$add_root/lib> > #export PATH=$add_root/bin> >> > export
> KDEDIRS=$add_root:> > export PATH=$add_root/bin:$PATH> > export
> LD_LIBRARY_PATH=$add_root/lib> > $add_root/bin/digikam> >> > Any help would
> be much apprecheated.> > Thanks in advance!>> I suspect a wrong install.
> Have you used .configure --prefix=myhomepath ? Yes I did. A wrong install
> is very unlikely the problem cause I first tried it with a copy of my last
> working install and then with a fresh install - both have the same problem.
>
> > What 'locate libdigikam.la kio_digikamtags.so' done on your computer ?
>
> # locate
> libdigikam.la/home/sero/kde_svn/testbuilds/digikam_trunk-0424/lib/libdigika
>m.la This is fine cause I have a symlink digikam_trunk -->
> digikam_trunk-0424 # locate kio_digikam.so
> Upps: NOTHING! Where does this belong to? OK, I will do a fresh install
> again! Thanks Gilles. Hope this fixes my problem.

Well in my computer, i install digiKam using --prefix=/usr. The result is :

$ locate libdigikam.la kio_digikamtags.so
/usr/lib/libdigikam.la
/home/gilles/Documents/Devel/SVN/trunk/extragear/graphics/digikam/digikam/.libs/libdigikam.lai
/home/gilles/Documents/Devel/SVN/trunk/extragear/graphics/digikam/digikam/.libs/libdigikam.la
/home/gilles/Documents/Devel/SVN/trunk/extragear/graphics/digikam/digikam/libdigikam.la
/home/gilles/Documents/Devel/SVN/stable/digikam/digikam/.libs/libdigikam.lai
/home/gilles/Documents/Devel/SVN/stable/digikam/digikam/.libs/libdigikam.la
/home/gilles/Documents/Devel/SVN/stable/digikam/digikam/libdigikam.la
/usr/lib/kde3/kio_digikamtags.so
/home/gilles/Documents/Devel/SVN/trunk/extragear/graphics/digikam/kioslave/.libs/kio_digikamtags.so
/home/gilles/Documents/Devel/SVN/stable/digikam/kioslave/.libs/kio_digikamtags.so

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] Install in /home borked - what did I do wrong?

Sebastian Roeder
In reply to this post by Sebastian Roeder
Am Dienstag, 25. April 2006 16:16 schrieb [hidden email]:

> Well in my computer, i install digiKam using --prefix=/usr. The result is :
>
> $ locate libdigikam.la kio_digikamtags.so
> /usr/lib/libdigikam.la
> /home/gilles/Documents/Devel/SVN/trunk/extragear/graphics/digikam/digikam/.
>libs/libdigikam.lai
> /home/gilles/Documents/Devel/SVN/trunk/extragear/graphics/digikam/digikam/.
>libs/libdigikam.la
> /home/gilles/Documents/Devel/SVN/trunk/extragear/graphics/digikam/digikam/l
>ibdigikam.la
> /home/gilles/Documents/Devel/SVN/stable/digikam/digikam/.libs/libdigikam.la
>i
> /home/gilles/Documents/Devel/SVN/stable/digikam/digikam/.libs/libdigikam.la
> /home/gilles/Documents/Devel/SVN/stable/digikam/digikam/libdigikam.la
> /usr/lib/kde3/kio_digikamtags.so
> /home/gilles/Documents/Devel/SVN/trunk/extragear/graphics/digikam/kioslave/
>.libs/kio_digikamtags.so
> /home/gilles/Documents/Devel/SVN/stable/digikam/kioslave/.libs/kio_digikamt
>ags.so
>
> Gilles

Me again. In the last hours I read the Gentoo docs concerning environment
variables and learned quite a lot. I am almost sure that it is a problem with
the LDPATH variable, that usaly points to all the places were libs can be
found.

Reading your output I found out that all the files I need are there, but
digikam seems not to find them:

~/kde_svn/testbuilds/digikam_trunk-0425/lib/kde3 $ ls -al
insgesamt 5836
drwxr-xr-x 2 sero sero   4096 25. Apr 16:11 .
drwxr-xr-x 4 sero sero   4096 25. Apr 16:11 ..
-rwxr-xr-x 1 sero sero   2375 25. Apr 16:02 kio_digikamalbums.la
-rwxr-xr-x 1 sero sero 288856 25. Apr 16:02 kio_digikamalbums.so
-rwxr-xr-x 1 sero sero   2328 25. Apr 16:02 kio_digikamdates.la
-rwxr-xr-x 1 sero sero  50876 25. Apr 16:02 kio_digikamdates.so
-rwxr-xr-x 1 sero sero   2334 25. Apr 16:02 kio_digikamsearch.la
-rwxr-xr-x 1 sero sero  66479 25. Apr 16:02 kio_digikamsearch.so
-rwxr-xr-x 1 sero sero   2322 25. Apr 16:01 kio_digikamtags.la
-rwxr-xr-x 1 sero sero  43118 25. Apr 16:01 kio_digikamtags.so
-rwxr-xr-x 1 sero sero   2390 25. Apr 16:01 kio_digikamthumbnail.la
-rwxr-xr-x 1 sero sero 510029 25. Apr 16:01 kio_digikamthumbnail.so

Gilles what does "echo $LDPATH" or "echo $LD_LIBRARY_PATH" give you? The
latter it not used in Gentoo it seems. Any pointers how I can make digikam
find the libs? Once I sort out this problem I can write a nice little blog
about this "home dir approach" of installing SVN snapshots ;-)  
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] Install in /home borked - what did I do wrong?

Bugzilla from thorsten.schnebeck@gmx.net
Am Dienstag 25 April 2006 19:07 schrieb Sebastian Röder:

> Me again. In the last hours I read the Gentoo docs concerning environment
> variables and learned quite a lot. I am almost sure that it is a problem
> with the LDPATH variable, that usaly points to all the places were libs can
> be found.
>
> Reading your output I found out that all the files I need are there, but
> digikam seems not to find them:

>
> Gilles what does "echo $LDPATH" or "echo $LD_LIBRARY_PATH" give you? The
> latter it not used in Gentoo it seems. Any pointers how I can make digikam
> find the libs? Once I sort out this problem I can write a nice little blog
> about this "home dir approach" of installing SVN snapshots ;-

Gentoo use a dynamic configuration of LDPATH:

You put a config file into /etc/env.d like

/etc/env.d/51digikam-svn with a content like

PATH="/your/path/bin"
LDPATH="/your/path/lib"

then you run
env-update and now you have a new /etc/ld.so.conf and the system knows where
to find your lib.

But you can also take the script from
http://forum.ebv4linux.de/viewtopic.php?t=747
and use the script in PATH startup method:
[...]
 cat > /usr/bin/digikam-svn << EOF
 #!/bin/sh
 export LDPATH="$MYDIR/lib:$LDPATH"
 export KDEDIRS="$MYDIR:$KDEDIRS"
 $MYDIR/bin/digikam
 EOF
 chmod a+x  /usr/bin/digikam-svn

But watch out that this script runs with the same userconfig, so you need to
setup a testuser to separate the userconfigs.

HTH

  Thorsten



_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] Install in /home borked - what did I do wrong?

Sebastian Roeder
In reply to this post by Sebastian Roeder
OK I might be one step further but still very confused by the problem.

I have updated my startscript and added some "feetback" - the new script looks
like this:

#!/bin/bash
# A little wrapper script to start the latest digikam testbuild

add_root=/home/sero/kde_svn/testbuilds/digikam_trunk
export KDEDIRS="${KDEDIRS}:$add_root"
echo "Adjusted KDEDIRS: ${KDEDIRS}"
export PATH="${PATH}:$add_root/bin"
echo "Adjusted PATH: ${PATH}"
#kbuildsycoca
digikam


The funny thing is that this script works perfect when started as root (note
that kbuildsycoca is started automatically also I didn't explicitly started
it):

~ # sh /home/sero/bin/start_digikam.sh
Adjusted KDEDIRS: /usr:/home/sero/kde_svn/testbuilds/digikam_trunk
Adjusted
PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.4.5:/opt/sun-jdk-1.4.2.10/bin:/opt/sun-jdk-1.4.2.10/jre/bin:/opt/sun-jdk-1.4.2.10/jre/javaws:/usr/kde/3.5/sbin:/usr/kde/3.5/bin:/usr/qt/3/bin:/home/sero/kde_svn/testbuilds/digikam_trunk/bin
kbuildsycoca running...
digikam: ScanLib: Finding non-existing Albums: 2 ms
digikam: ScanLib: Finding items not in the database or disk: 209 ms
digikam: ScanLib: Updating items without date: 0 ms
digikam: Cannot parse EXIF metadata using Exiv2
digikam: ImagePlugin_Core plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
digikam: ImagePlugin_RainDrop plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_RainDrop
digikam: ImagePlugin_InPainting plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_InPainting
digikam: ImagePlugin_Infrared plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Infrared
digikam: ImagePlugin_Texture plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Texture
digikam: ImagePlugin_Border plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Border
digikam: ImagePlugin_OilPaint plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_OilPaint
digikam: ImagePlugin_InsertText plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_InsertText
digikam: ImagePlugin_Emboss plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Emboss
digikam: ImagePlugin_NoiseReduction plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_NoiseReduction
digikam: ImagePlugin_Unsharp plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Unsharp
digikam: ImagePlugin_HotPixels plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_HotPixels
digikam: ImagePlugin_AdjustLevels plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_AdjustLevels
digikam: ImagePlugin_ShearTool plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_ShearTool
digikam: ImagePlugin_Solarize plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Solarize
digikam: ImagePlugin_DistortionFX plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_DistortionFX
digikam: ImagePlugin_LensDistortion plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_LensDistortion
digikam: ImagePlugin_FilmGrain plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_FilmGrain
digikam: ImagePlugin_BlowUp plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_BlowUp
digikam: ImagePlugin_Restoration plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Restoration
digikam: ImagePlugin_SuperImpose plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_SuperImpose
digikam: ImagePlugin_Refocus plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Refocus
digikam: ImagePlugin_WhiteBalance plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_WhiteBalance
digikam: ImagePlugin_BlurFX plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_BlurFX
digikam: ImagePlugin_AntiVignetting plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_AntiVignetting
digikam: ImagePlugin_AdjustCurves plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_AdjustCurves
digikam: ImagePlugin_FreeRotation plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_FreeRotation
digikam: ImagePlugin_Perspective plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Perspective
digikam: ImagePlugin_ChannelMixer plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_ChannelMixer
digikam: ImagePlugin_Charcoal plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Charcoal

The problem now is that it doesn't start as normal user:

~ $ sh bin/start_digikam.sh
Adjusted KDEDIRS: /usr:/home/sero/kde_svn/testbuilds/digikam_trunk
Adjusted
PATH: /usr/kde/3.5/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.4.5:/opt/sun-jdk-1.4.2.10/bin:/opt/sun-jdk-1.4.2.10/jre/bin:/opt/sun-jdk-1.4.2.10/jre/javaws:/usr/kde/3.5/bin:/usr/qt/3/bin:/home/sero/kde_svn/testbuilds/digikam_trunk/bin
digikam: ScanLib: Finding non-existing Albums: 3 ms
digikam: ScanLib: Finding items not in the database or disk: 208 ms
digikam: ScanLib: Updating items without date: 0 ms
digikam: Cannot parse EXIF metadata using Exiv2
digikam: ImagePlugin_Core plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core
digikam: ImagePlugin_RainDrop plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_RainDrop
digikam: ImagePlugin_InPainting plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_InPainting
digikam: ImagePlugin_Infrared plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Infrared
digikam: ImagePlugin_Texture plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Texture
digikam: ImagePlugin_Border plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Border
digikam: ImagePlugin_OilPaint plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_OilPaint
digikam: ImagePlugin_InsertText plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_InsertText
digikam: ImagePlugin_Emboss plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Emboss
digikam: ImagePlugin_NoiseReduction plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_NoiseReduction
digikam: ImagePlugin_Unsharp plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Unsharp
digikam: ImagePlugin_HotPixels plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_HotPixels
digikam: ImagePlugin_AdjustLevels plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_AdjustLevels
digikam: ImagePlugin_ShearTool plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_ShearTool
digikam: ImagePlugin_Solarize plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Solarize
digikam: ImagePlugin_DistortionFX plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_DistortionFX
digikam: ImagePlugin_LensDistortion plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_LensDistortion
digikam: ImagePlugin_FilmGrain plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_FilmGrain
digikam: ImagePlugin_BlowUp plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_BlowUp
digikam: ImagePlugin_Restoration plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Restoration
digikam: ImagePlugin_SuperImpose plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_SuperImpose
digikam: ImagePlugin_Refocus plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Refocus
digikam: ImagePlugin_WhiteBalance plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_WhiteBalance
digikam: ImagePlugin_BlurFX plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_BlurFX
digikam: ImagePlugin_AntiVignetting plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_AntiVignetting
digikam: ImagePlugin_AdjustCurves plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_AdjustCurves
digikam: ImagePlugin_FreeRotation plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_FreeRotation
digikam: ImagePlugin_Perspective plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Perspective
digikam: ImagePlugin_ChannelMixer plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_ChannelMixer
digikam: ImagePlugin_Charcoal plugin loaded
digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Charcoal
digikam: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Fehler beim Laden von "kio_digikamdates"
digikam:
digikam: WARNING: [void Digikam::AlbumManager::slotResult(KIO::Job*)] Failed
to list dates
digikam: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Fehler beim Laden von "kio_digikamalbums"
digikam:
digikam: WARNING: Failed to list url: Could not start process Unable to create
io-slave:
klauncher said: Fehler beim Laden von "kio_digikamalbums"

Calling kbuildsycoca manualy from the script didn't change anything - but it
complains about kio database and a lot about mime types:

kbuildsycoca running...
Reusing existing ksycoca
kio (KSycoca): ERROR: No database available!
kbuildsycoca: WARNING: '/usr/kde/3.5/share/applications/kde/ark.desktop'
specifies undefined mimetype/servicetype 'application/x-tbz2'
kbuildsycoca: WARNING: 'ark_part.desktop' specifies undefined
mimetype/servicetype 'application/x-tbz2'
kbuildsycoca: WARNING: 'kfile_ooo.desktop' specifies undefined
mimetype/servicetype 'application/vnd.sun.xml.writer.global'
kbuildsycoca: WARNING: 'kfile_ooo.desktop' specifies undefined
mimetype/servicetype 'application/vnd.sun.xml.writer.math'
kbuildsycoca: WARNING: '/usr/share/applications/scribus.desktop' specifies
undefined mimetype/servicetype 'application/x-scribus'
kbuildsycoca: WARNING: '/usr/share/applications/kde/amarok.desktop' specifies
undefined mimetype/servicetype 'application/asx'
kbuildsycoca: WARNING: '/usr/share/applications/kde/amarok.desktop' specifies
undefined mimetype/servicetype 'audio/midi'
kbuildsycoca: WARNING: '/usr/share/applications/kde/amarok.desktop' specifies
undefined mimetype/servicetype 'audio/x-aac'
kbuildsycoca: WARNING: '/usr/share/applications/kde/amarok.desktop' specifies
undefined mimetype/servicetype 'audio/x-m4a'
kbuildsycoca: WARNING: 'Office/krita_magick.desktop' specifies undefined
mimetype/servicetype 'image/x-xcf'
kbuildsycoca: WARNING: 'katepart.desktop' specifies undefined
mimetype/servicetype 'text/x-fortran'
kbuildsycoca: WARNING: 'kcertpart.desktop' specifies undefined
mimetype/servicetype 'application/binary-certificate'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/mp3'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/mpg'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-mpeg'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-mpg'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/wav'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-pn-wav'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-pn-windows-acm'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-pn-windows-pcm'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'text/vnd.rn-realtext'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'application/vnd.rn-realmedia-secure'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'application/vnd.rn-realaudio-secure'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-realaudio-secure'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'video/vnd.rn-realvideo-secure'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-realaudio'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'application/vnd.rn-realmedia-vbr'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'image/vnd.rn-realpix'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'application/vnd.rn-realsystem-rmj'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'application/vnd.rn-realsystem-rmx'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-aac'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/m4a'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-m4a'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/mp2'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/mp1'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-mp1'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/rn-mpeg'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/scpls'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'application/x-smil'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'application/streamingmedia'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'application/x-streamingmedia'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'application/sdp'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-pn-au'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/aiff'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-pn-aiff'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'video/3gpp'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'video/3gpp-encrypted'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/3gpp'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/3gpp-encrypted'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/amr'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/amr-encrypted'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/amr-wb'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/amr-wb-encrypted'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-rn-3gpp-amr'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-rn-3gpp-amr-encrypted'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-rn-3gpp-amr-wb'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-rn-3gpp-amr-wb-encrypted'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'video/3gpp2'
kbuildsycoca: WARNING: '/usr/share/applications/realplay.desktop' specifies
undefined mimetype/servicetype 'audio/x-3gpp2'
kbuildsycoca: WARNING: '/usr/share/applications/xine.desktop' specifies
undefined mimetype/servicetype 'video/x-anim'
kbuildsycoca: WARNING: 'knotify.desktop' specifies undefined
mimetype/servicetype 'KNotify'
kbuildsycoca: WARNING:
'/usr/share/applications/openoffice.org-2.0-base.desktop' specifies undefined
mimetype/servicetype 'application/vnd.oasis.opendocument.database'
kbuildsycoca: WARNING:
'/usr/share/applications/openoffice.org-2.0-writer.desktop' specifies
undefined mimetype/servicetype 'application/vnd.oasis.opendocument.text-web'
kbuildsycoca: WARNING:
'/usr/share/applications/openoffice.org-2.0-writer.desktop' specifies
undefined mimetype/servicetype
'application/vnd.oasis.opendocument.text-master'
kbuildsycoca: WARNING:
'/usr/share/applications/openoffice.org-2.0-writer.desktop' specifies
undefined mimetype/servicetype 'application/vnd.sun.xml.writer.global'
kbuildsycoca: WARNING:
'/usr/share/applications/openoffice.org-2.0-writer.desktop' specifies
undefined mimetype/servicetype 'application/x-doc'
kbuildsycoca: WARNING:
'/usr/share/applications/openoffice.org-2.0-writer.desktop' specifies
undefined mimetype/servicetype 'application/vnd.wordperfect'
kbuildsycoca: WARNING:
'/usr/share/applications/openoffice.org-2.0-math.desktop' specifies undefined
mimetype/servicetype 'application/vnd.sun.xml.math'

Now I am completely lost! Is my KDE borked? What can I do?
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] Install in /home borked - what did I do wrong?

Sebastian Roeder
In reply to this post by Sebastian Roeder
Am Dienstag, 25. April 2006 21:49 schrieb [hidden email]:
> Gentoo use a dynamic configuration of LDPATH:
> You put a config file into /etc/env.d

Thanks Thorsten! I alraedy read this in the handbook and you encouraged me to
try it. For me this is not the best solution (cause I like to keep such
custom stuff in my home dir and not as deep in the system as /etc/env.d) BUT:
this is the only way that works!

 $ cat /etc/env.d/46digikam-svn
KDEDIRS=/home/sero/kde_svn/testbuilds/digikam_trunk
LDPATH=/home/sero/kde_svn/testbuilds/digikam_trunk/lib
PATH=/home/sero/kde_svn/testbuilds/digikam_trunk/bin

> then you run
> env-update and now you have a new /etc/ld.so.conf and the system knows
> where to find your lib.

> But you can also take the script from
> http://forum.ebv4linux.de/viewtopic.php?t=747
> and use the script in PATH startup method:
> [...]
>  cat > /usr/bin/digikam-svn << EOF
>  #!/bin/sh
>  export LDPATH="$MYDIR/lib:$LDPATH"
>  export KDEDIRS="$MYDIR:$KDEDIRS"
>  $MYDIR/bin/digikam
>  EOF
>  chmod a+x  /usr/bin/digikam-svn

That's close to my own startup script but this doens't work (the LDPATH is not
processed by Gentoo in any way it seems. Try echo $LDPATH in your system -
$LDPATH is empty by default).

> But watch out that this script runs with the same userconfig, so you need
> to setup a testuser to separate the userconfigs.

No problem cause atm I have only this SVN install. What was interessting in
the whole story is that it seems like my older SVN install has allways been a
mixture from SVN and stable Gentoo stuff without me knowing it. But now
finally it is sane ;-)

> HTH
Yeahhh it did! Thank you so much!

Good night
Sero
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] Install in /home borked - what did I do wrong?

Bugzilla from thorsten.schnebeck@gmx.net
In reply to this post by Sebastian Roeder
Am Dienstag 25 April 2006 21:49 schrieb Sebastian Röder:

> I have updated my startscript and added some "feetback" - the new script
> looks like this:
>
> #!/bin/bash
> # A little wrapper script to start the latest digikam testbuild
>
> add_root=/home/sero/kde_svn/testbuilds/digikam_trunk
> export KDEDIRS="${KDEDIRS}:$add_root"
> echo "Adjusted KDEDIRS: ${KDEDIRS}"
> export PATH="${PATH}:$add_root/bin"
> echo "Adjusted PATH: ${PATH}"
> #kbuildsycoca
> digikam
>
>

I miss an
export LDPATH="$/add_root/lib:$LDPATH
in your script and you should put your path on top of the searchlist otherwise
digiKam in system dirs will be used. So better use
export PATH="$add_root/bin:${PATH}"

HTH

  Thorsten

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