I built KDE from sources (branch KDE/4.7). What I built:
akonadi
attica
automoc
cagibi
kate
kde-baseapps
kdelibs
kdepim
kdepimlibs
kde-runtime
kdesupport
kde-workspace
konsole
networkmanagement
polkit-qt-1
soprano
strigi
..not in that order though...

I run a KDE-session setting the following variables:

export KDEDIR=$HOME/kde-dev/inst/kde-master
export LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH
export PATH=$KDEDIR/bin/:$PATH
export QTDIR=/usr
export KDEHOME=$HOME/kdehome-kde-master

When I login to this session there is an error "installing the virtuoso soprano plugin is mandatory for using nepomuk"

Though when building soprano it clearly states that all external dependencies where found and the virtuoso backend ist built.
Also in ~/kde-dev/inst/kde-master/lib/soprano I can find libsoprano_virtuosobackend.so

Also: on the same system I am running the default KDE installed from distro packages (4.7.1) so any other runtime dependency needed for nepomuk/virtuoso should be there and found in /usr/lib64 or whereever.

I run the distro-package-KDE session as user thomas and the source-built-KDE session as user kde-dev.
Any ideas why the virtuoso-backend is not found for user kde-dev???


Thanks,
Thomas

I suppose here that the problem lies in setting right variables for running KDE. For instance :
export KDEDIR=$HOME/kde-dev/inst/kde-master
export KDEHOME=$HOME/kdehome-kde-master
seems confusing, what is 'kdehome-kde-master' ?

I don't know at all if it's the way you start kde the problem. It seems you start kde from another DM session or from the command line in some way that is not clear, and that you don't use the starkde script. This script is found in <NEW_KDE_HOME>/bin. You can just run it from the command line and it would set all paths for executables and libraries rightly.

I would suggest another way that works with kdm and gdm :

cp /usr/share/xsessions/kde.desktop /usr/share/xsessions/kdenew.desktop

Edit kdenew.desktop

Update :

Exec=<NEW_KDE_HOME>/bin/startkde
TryExec=<NEW_KDE_HOME>/bin/startkde
Name=KDE_NEW

Restart X and you should see an entry KDE_NEW in kdm or gdm.

Hi there,

I was struggling with the same problem in a similar setup. After finding this post (http://lists.semanticdesktop.org/pipermail/nepomuk-kde/2010-February/000623.html), I saw that the file it's looking for comes from my distributions repositories, and is located in /usr/lib64 in my case. After prepending that to my LD_LIBRARY_PATH I was able to get kcmshell4 kcm_nepomuk to display the settings etc.

Perhaps you're having the same problem? Might be worth trying anyway