DSSI "path not found" after upgrade to Etch
 

I've already posted this to the Debian-user list, but they seem to get so easily distracted to OT stuff that my post has possibly been missed.

I've always had good responses here, so here goes.

Today 17:06:28

I'd appreciate a bit of help to fix this problem.

I had DSSI plugins installed on Sarge from Willem Engen's repo, and they had
been working ok, but since upgrading to Etch, the desktop launchers fail to
work. Trying as user on the CLI with the same command, I got a DSSI "path not
found", and the plugin obviously doesn't load.

The path was "jack-dssi-host whysynth.so" as an example, and if I changed it
on the desktop launcher to the full path
"jack-dssi-host /usr/lib/dssi/0.9/whysynth.so" whysynth starts ok, and same
goes for the CLI.

I Googled DSSI_PATH , and a spanish blog suggested,
export DSSI_PATH=/usr/lib/dssi/0.9
followed by
echo $DSSI_PATH
which verified the path as /usr/lib/dssi/0.9

I can now load the dssi plugin on the CLI with "jack-dssi-host whysynth.so",
but the same command on the desktop launcher still won't work.

The spanish blog also suggested adding to ~/.bashrc
export DSSI_PATH=/usr/lib/dssi/0.9
Which I did by adding it to the bottom of the file (I havn't messed
with .bashrc before) , still no change from the destop launchers for the
plugins. Logged out of KDE, then back in, but no change.

Now I'm stuck.

Would ~/.bash_profile, which is also still at default status have any effect
on the entry I made in ~/.bashrc? I've put it below.

Last login: Mon Mar 19 14:41:29 2007
djmons@debian:~$ cat ~/.bash_profile
# ~/.bash_profile: executed by bash(1) for login shells.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

umask 022

# the rest of this file is commented out.

# include .bashrc if it exists

#if [ -f ~/.bashrc ]; then
# source ~/.bashrc
#fi

# set PATH so it includes user's private bin if it exists
#if [ -d ~/bin ] ; then
# PATH=~/bin:"${PATH}"
#fi

# do the same with MANPATH
#if [ -d ~/man ]; then
# MANPATH=~/man:"${MANPATH}"
#fi
djmons@debian:~$

Any help very much appreciated.

Nigel.aka farpoint.

The ~/.bash_profile or ~/.profile is run when you first log on, if you use the bash shell. The ~/.bashrc file is run everytime you open a console, such as konsole. You may wish to remove some comments from ~/.profile:
This will source ~/.bashrc when you first log in.

Also, double check on which libraries exits. Updating might have replaced one library version with another. For example maybe dssi/0.9/ is replaced with dsi/10.0/ or something like that. If there is a whysynth.so.10 instead, you produce a link from whysynth.so.9 to whysynth.so.10 for example.

Another thing you could try is adding the library path (e.g. "/usr/lib/dssi/0.9") /etc/ld.so.conf and then run as root the command "ldconfig".

You could also use the ldd command to list the libraries that the binaries will load, assuming they weren't stripped.

Many thanks. Uncommenting those 3 lines in ~/bash_profile has fixed the problem. Now the desktop launchers for the DSSI plugins work ok.

An unrelated question. You have used a heading "Code:", which has a box beneath it with the code in it. How do I do this. It's always been a bit of a mystery to me.

Thanks again for the fix to my problem.

Nigel. aka farpoint.

Type in the word "code" between square brackets at the beginning of a code sample, and "/code" between square brackets at the end.

Thanks for that. I have tested it as a preview on this post, and it works like magic.

btw. I still havn't received a reply from the Debian-users list over the DSSI_PATH problem which you gave me the answer to.

This forum has always been very helpfull to me, whether that is for Debian, Fedora, or Slackware problems.

Nigel. aka farpoint.