Hi,

when i try to run the daily build i see:

cvts@xdap:~/Téléchargements/kdenlive/kdenlive$ ./start-kdenlive
Way to run = Normal
running kdenlive
kdenlive: error while loading shared libraries: libnepomuk.so.4: cannot open shared object file: No such file or directory
cvts@xdap:~/Téléchargements/kdenlive/kdenlive$

The error come on two machines after migration from 14.04 to 14.10

Thanks

apt-get install libnepomuk4

it does not work .. your package is not found ..

cvts@xdap:~$ sudo apt-get install libnepomuk4
[sudo] password for cvts:
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Aucune version du paquet libnepomuk4 n'est disponible, mais il existe dans la base
de données. Cela signifie en général que le paquet est manquant, qu'il est devenu obsolète
ou qu'il n'est disponible que sur une autre source

E: Le paquet « libnepomuk4 » n'a pas de version susceptible d'être installée
cvts@xdap:~$

You may have to try installing nepomuk from source....

http://dev.nepomuk.semanticdesktop.org/

hi
Maybe i find a very ugly solution ...
In the folder of the lib of the local kdenlive, i copy and rename a lib to libnepomuk.so.4 ..

It's seem to work ...

...

that is indeed an ugly solution, you should never rename library files as other software will now not work

sure it's a ugly solution but it's the only one i know ...

it's not really a big problem, because the dev version is isolated in a directory and launch with a specifical launcher with export variables ....
this solution doesn't impact the whole system ..

nyme

nymen wrote:sure it's a ugly solution but it's the only one i know ...

it's not really a big problem, because the dev version is isolated in a directory and launch with a specifical launcher with export variables ....
this solution doesn't impact the whole system ..

nyme

good point. i didn't mean to come off the way i did. when a solution is the only way than i understand. i do it sometimes, maybe.....

Hey guys is there a *proper* solution for this? I am getting the same problem

Thanks

vjoe wrote:Hey guys is there a *proper* solution for this? I am getting the same problem

Thanks

As long as you are running the daily build version which runs from its own sandbox away from other stuff, and the file you rename is inside the sand box folder, then the rename trick appears to be a workable solution

Isn't there a risk of renaming the wrong file?

Well if you unzip the daily build to /home/vjoe/kdenlive_daily and then rename a file in /home/vjoe/kdenlive_daily/kdenvlive/lib/blah blah then no. There is no risk of that. Because you know you are renaming a file that you just deployed.

Ah, so shall I put a new dummy file there instead?

I'll ask the people preparing the daily builds (MLT devs) to remove nepomuk dependency from the script; or maybe will completely remove it from code (it disappears anyway in future KF5 version).