Re: Resolved: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.

[Seeker <seeker5528@comcast.net>]

On 9/23/2016 10:28 AM, Brian wrote:
> On Fri 23 Sep 2016 at 10:07:43 -0700, Seeker wrote:
>
> > On 9/22/2016 6:18 PM, Seeker wrote:

<Snip>


> > In spite of the existence of 60xprofile and the fact that '~/.xprofile' did
> > get sourced in the ast, I'm not finding any information on when you
> > might expect xprofile/.xprofile to get sourced or not sourced.
>
> To the very best of my knowledge ~/.xprofile has never been a feature of
> Debian's X configuration files in /etc/X11. However, it is acted on by
> gdm3 in *its* Xsession script.
>
> What does
>
>   dpkg -S /full/path/to/60xprofile
>
> give you?

It tells me 'no path found matching pattern'

Looks like a leftover from something possibly non-debian. Last modified
date 2007 if you trust that to mean anything.

Running cruft on the system now to see what it has to report.

The list of unexaplained files is big, but outside of 60xprofile and
stuff in '/usr/src' it mostly looks like autogenerated stuff.

I still have a directory in /usr/src for the 2.4.23 kernel and google
tells me that was released Nov 2003, so it's been sometime before that
since I've done a clean install. Following unstable the whole time and
making the transition from 32bit to 64bit the hard way somewhere along
the way. I have had my binge and 'dpkg --purge --force-depends' moments
along the way where I looked for and deleted related orphaned stuff
before re-installing some or all of the purged packages, but it seems
reasonable to expect I didn't get all the orphaned stuff along the way.

> > So it looks like '~/.xsessionrc' is way to go.
>
> For what? In what circumstance?

For me personally, I only ever remember using .profile/.xprofile to set
environment variables (my memory is terrible). The path mainly, but 
other things come up once in a while. Seemed like it was short lived,
but there was a variable that could be set to make
'Ctrl'+'Alt'+'Backspace' work in your X session. I had a locale issue
at one point, so was setting the locale in .profile/.xprofile (whatever
worked at the time) for a while, 'till I got that real issue sorted out.

These are the things I would use '~/.xsessionrc' for.

> > I guess the next question would be....
> >
> > Can we expect this to continue working over the long haul with a Wayland
> > session or will we have to start putting things into
> > '~/.config/autostart/'?
>
> Pass.

It has it's uses.

If I want a program to run independently of what desktop session I am
running, I create a .desktop file or grab an existing one and modify it,
then put it in '~/.config/autostart/'.

https://linuxcritic.wordpress.com/2010/04/07/anatomy-of-a-desktop-file/

I made a copy of '/etc/xdg/autostart/pulseaudio.desktop' in my
'~/.config/autostart/' and changed 'Exec=start-pulseaudio-x11' to
'Exec=' so pulse doesn't start automatically but is still available.
KDE did have it's own .desktop file for starting pulseaudio, but I
don't currently see one in '/etc/xdg/autostart' there may or may not
still be one in a KDE specific directory, I do have a
pulseaudio-kde.desktop file in my autostart that also has the target of
the 'Exec=' line removed.

Later, Seeker