It was suggested to me to try and use 0.0.0.0 localhost in my /etc/hosts file, bu that's not doing anything. 

With netstat I'm seeing that both jack-dssi-host and WhySynth_gtk are opening ports, but the GUI still doesn't open up. 

What I'm seeing is this:

[sean@localhost ~]$ jack-dssi-host whysynth.so

jack-dssi-host: Warning: DSSI path not set
jack-dssi-host: Defaulting to "/usr/local/lib64/dssi:/usr/lib64/dssi:/usr/local/lib/dssi:/usr/lib/dssi:/home/sean/.dssi"


jack-dssi-host: OSC URL is:
osc.udp://localhost:19884/dssi/whysynth/WhySynth/chan00

host: Ready
WhySynth_gtk starting (pid 22764)...

----
and this from netstat....

udp        0      0 *:19884                 *:*                                 22757/jack-dssi-hos 
udp        0      0 *:19885                 *:*                                 22764/WhySynth_gtk 

Sean


On Mon, May 13, 2013 at 11:41 PM, Sean Beeson <seanbeeson@gmail.com> wrote:
Hi, list. 

Anyone familiar with WhySynth issues and perhaps OSC? When I run Whysynth it starts fine and the GUI starts. Sound works, but the GUI doesn't open. I have read this issue is caused by the computer's name not resolving, but mine does resolve, so something else is causing this. I turned off iptables to see if it was a firewall issue and that didn't help much. 

Since the DSSI and GUI run and sound works, but the GUI doesn't show, I am thinking it still may be an issue with a port or some other OSC issue. I am not so familiar with trouble-shooting OSC. Anyone got any pointers on trouble-shooting it. What utilities are there? 

Could it be some other trouble?

Thanks,

Sean