On Wed, 4 Dec 2024 21:07:00 -0500, bent fender <slowroller@trixtar.org> wrote:
There's nothing wrong with the script that executes xeyes but there is something wrong with me when I call that script from within ~/.profile. It's something I've been warned about before (I think Carlos obliged once) but I just wouldn't listen.
The way it was being called: bash my-xeyes-launch.bsh
The way it should and now is being called: my-xeyes-launch.bsh
I should be ashamed of it but that has never been one of my habbits. It would be nice though to understand HOW this makes a difference? With the latter (correct) call the low-res screen (initially thrown by ssdm or whatever DM being used) is free of the two pairs of eyeballs. As soon as as I use the former (wrong) call they are there again.
Well, this involves a bit of conjecture, but I have determined that you had inadvertently included this code in your launch script: #!/bin/sh four_eyes() { if [ "$desktop" = "kde" ] then echo "it is kde" xeyes -geometry 70x50+36+420 & xeyes -geometry 70x50-36+420 & else echo "No kde, no xeyes" fi } four_eyes # For bash, be extra certain that the xeyes are there if expr "/${BASH-}" : '.*/bash$' >/dev/null ;then sleep 6 four_eyes fi
Thanks to all for hints to keep me trying, especially Robert.
You're very welcome, Bent. -- Robert Webb ;-)