Subject: Re: Failed to execute child process (no such file or directory) ...

From: "Thomas Schmitt" <[email-masked]>
Date: Wed, 21 Sep 2016 17:20:31 +0200

Hi,

Anthony Baldwin wrote:
> giving the full path in the rc.xml doesn't seem to make
> any difference.

Are you sure openbox is aware of the change ?
(Did you restart it ? Does it react immediately on newly added
 key combinations ?)

> Yes, the $PATH is set in my .bashrc...
> Wait.. Is this why I can start them in a terminal, but openbox can't?

Possibly.

It depends on when and by what entity the openbox window manager was
started and whether it uses PATH to find commands.
If the starter was some kind of shell, then it probably has forwarded
its own PATH variable to openbox. If it was something more fancy, then
behavior depends on the mood of its developers.

You could put a script into /usr/bin (where it will be found, i hope),
let it print the PATH to a file, bind it to a key combination, and
look what it writes into the file:
  #!/bin/sh
  echo "$PATH" >/tmp/my_openbox_test_for_PATH

But if PATH was to blame, then an absolute program path should have
helped. If it came into effect, that is.

Have a nice day :)

Thomas

---

From: Anthony Baldwin <[email-masked]>
Date: Wed, 21 Sep 2016 14:12:58 -0400

> (Did you restart it ? Does it react immediately on newly added

Normally, yes, OBx would, indeed reload, the configurations in its 
rc.xml file upon a --restart and immediately implement any changes.
> helped. If it came into effect, that is.

So it's not likely a path problem it seems..

Thanks,
Tony

-- 
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT

---

From: Greg Wooledge <[email-masked]>
Date: Wed, 21 Sep 2016 11:23:32 -0400

>   echo "$PATH" >/tmp/my_openbox_test_for_PATH

Or you can use  ps eww -p "$(pgrep openbox)"  (or directly substitute
the PID you want in case that command substitution is wrong; it works
for me with fvwm).  The PATH should be visible in the process's
environment as displayed by ps.  There may be a lot of noise to filter
out, of course.

---

From: Anthony Baldwin <[email-masked]>
Date: Wed, 21 Sep 2016 10:59:52 -0400

Sorry that you're getting this twice again, Thomas,
but I keep flummoxing the list-reply function (old age + brain tumor).

Tony

On 09/21/2016 09:54 AM, Thomas Schmitt wrote:
> Hi,
>
> Tony Baldwin wrote:
>> .config/openbox/rc.xml
>>         <command>bid</command>
>
> Well, a short while ago with cron it helped to tell the clueless
> software where the script is by an absolute path.
> Probably:
>
>         <command>/home/tony/bin/bid</command>

I just tried, and giving the full path in the rc.xml doesn't seem to 
make any difference.
>
>> Shortuts for stuff in /bin/ or /usr/bin/ [...] seem to work fine
>
> What user started the software ? And when ?
I'm the only user on this system.
Does when really matter?
Every time/any time I get these errors now.
> Was PATH already set to the value you are seeing in the shell ?
Yes, the $PATH is set in my .bashrc...
Wait.. Is this why I can start them in a terminal, but openbox can't?
Because the path is being set in my .bashrc, and, thus, only for shells 
I open?
When I switch to su, echo $PATH, of course, gives a different response
(includes /sbin/ stuff, but not $HOME anything),
If this is the problem, how to I get my $HOME/bin permanently in the 
path so openbox can run stuff from there, too?