On Thu, 5 Dec 2024 08:21:55 -0500, bent fender <slowroller@trixtar.org> wrote:
Thu, 5 Dec 2024 11:27:58 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-12-05 03:07, bent fender wrote:
The way it was being called: bash my-xeyes-launch.bsh
Since the first line of your script is '#!/bin/sh', you should use 'sh' instead of 'bash' when calling it as an argument to a shell invocation. That will avoid surprises, although for the script as it is, it won't matter. You have followed up with news that the double execution problem has gone away with your new graphics board. The software problem still exists, though, ready to bite again. I believe the script is being called also from some other piece of software besides the above line in your ~/.profile . To enable easy current and future debugging, I suggest replacing the line with: if [ -e ~/.profile-disable_xeyes_launch ] ;then echo === .profile xeyes disabled: ~/.profile-disable_xeyes_launch >&2 else sh my-xeyes-launch.bsh fi Then, when you want to check whether there is something else invoking xeyes: $ touch ~/.profile-disable_xeyes_launch Just remove the file to put your .profile functioning back to normal. -- Robert Webb