Strange Eterm-problem

[PatrickBaer]

Good morning,

I recently added some ssh-logins as menu-items to the fluxbox menu:

[submenu] (SSH Sessions)
[exec] (Vader) {Eterm -n "SSH Vader" -e /usr/bin/ssh root@vader.tvwerk.de}
[exec] (Medusa 1) {Eterm -n "SSH Medusa 1" -e /usr/bin/ssh root@192.168.17.6}
[exec] (Medusa 2) {Eterm -n "SSH Medusa 2" -e /usr/bin/ssh root@192.168.17.7}
[exec] (Proxy1) {Eterm -n "SSH Proxy 1" -e /usr/bin/ssh root@10.10.10.2}
[exec] (Proxy2) {Eterm -n "SSH Proxy 2" -e /usr/bin/ssh root@10.10.10.3}
[exec] (R2D2) {Eterm -n "SSH R2D2" -e /usr/bin/ssh root@r2d2.tvwerk.de}
[exec] (Keto) {Eterm -n "SSH Keto" -e /usr/bin/ssh root@keto.tvwerk.de}
[end]


Now the strange thing: When I click the first entry "SSH Vader", it works just fine. I try the second one and the Eterm window comes up and immediately closes? I tried with some other lines and it seems some work and some not, just like the medusa lines, first doesn't, seconds works?

I replaced Eterm with xterm and all of the lines do work, strange eh?

What might that be.....

[ivanatora]

Try running these commands from a regular term (like xterm, aterm... something you have 100% working) and see if there are any errors after the ssh process exit.

[BSDfan666]

xterm is command-line compatible and the above options seem to work fine in my fluxbox menu, consider escaping the operand of -e as well, -e "/usr/bin/ssh root@vader.tvwerk.de" for instance.

If that doesn't work, try replacing the double quotes with single quotes...

[PatrickBaer]

Well all of your suggestions might be a good attempt.

But it still doesn't explain, why

[exec] (Medusa 1) {Eterm -n "SSH Medusa 1" -e /usr/bin/ssh root@192.168.17.6}

works like a charme, while

[exec] (Medusa 2) {Eterm -n "SSH Medusa 2" -e /usr/bin/ssh root@192.168.17.7}

boldly goes, where no man has gone before?

[BSDfan666]

Can't explain it, works here perfectly... perhaps there is some unprintable in the file that's causing problems.

[ivanatora]

PatrickBaer, where are you from? Does your language uses some strange encoding? Are you switching keyboard layouts a bit?
I'm asking becouse it is the DUMBEST mistake ever happened to me - change a lating 'a' with a cyrillic 'а'. Do you see the difference? There is no difference in graphical presentation, but for the PC they are completely different characters. And thus 'startx' is a valid cmd, but 'stаrtx' (cyr 'a') is a 'command not found'.
Just rewrite these entries that are bothering you.