Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #172580 > unrolled thread
| Started by | Tony Baldwin <tonybaldwin@gmx.com> |
|---|---|
| First post | 2016-09-21 15:50 +0200 |
| Last post | 2016-09-21 16:10 +0200 |
| Articles | 10 on this page of 50 — 15 participants |
Back to article view | Back to linux.debian.user
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. Tony Baldwin <tonybaldwin@gmx.com> - 2016-09-21 15:50 +0200
Re: Failed to execute child process (no such file or directory) ... "Thomas Schmitt" <scdbackup@gmx.net> - 2016-09-21 16:00 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-21 16:10 +0200
Re: 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. Tony Baldwin <tonybaldwin@gmx.com> - 2016-09-21 16:50 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-21 17:10 +0200
Re: 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. Anthony Baldwin <baldwinlinguas@gmx.com> - 2016-09-21 21:30 +0200
Re: 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. David Wright <deblis@lionunicorn.co.uk> - 2016-09-22 04:30 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 15:20 +0200
Re: 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. <tomas@tuxteam.de> - 2016-09-22 15:30 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 16:00 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-22 16:30 +0200
Re: 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. Ric Moore <wayward4now@gmail.com> - 2016-09-22 18:30 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-22 16:00 +0200
Re: 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. Tixy <tixy@yxit.co.uk> - 2016-09-22 16:20 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 17:00 +0200
Re: 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. Darac Marjal <mailinglist@darac.org.uk> - 2016-09-22 17:20 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-22 18:40 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 22:20 +0200
Re: 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. Dominic Knight <dominicknight@gmx.com> - 2016-09-23 01:30 +0200
Re: 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. Curt <curty@free.fr> - 2016-09-23 11:00 +0200
Re: 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. <tomas@tuxteam.de> - 2016-09-23 11:40 +0200
Re: 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. tomas@tuxteam.de - 2016-09-23 11:50 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-23 18:40 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-24 21:40 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-25 20:00 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-26 23:20 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-26 23:50 +0200
Re: 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> - 2016-09-27 07:50 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-27 14:30 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-27 16:20 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-27 16:40 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-27 18:00 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-27 18:10 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-27 21:00 +0200
Re: 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. "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu> - 2016-09-27 00:00 +0200
Re: 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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-27 14:30 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-22 18:00 +0200
Re: 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. Tixy <tixy@yxit.co.uk> - 2016-09-22 21:00 +0200
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. Tony Baldwin <tonybaldwin@gmx.com> - 2016-09-22 17:30 +0200
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> - 2016-09-22 18:10 +0200
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. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 18:20 +0200
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. Brian <ad44@cityscape.co.uk> - 2016-09-22 19:50 +0200
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> - 2016-09-23 03:30 +0200
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> - 2016-09-23 19:10 +0200
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. Brian <ad44@cityscape.co.uk> - 2016-09-23 19:30 +0200
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> - 2016-09-24 08:40 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-22 21:10 +0200
Re: 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. Brian <ad44@cityscape.co.uk> - 2016-09-22 21:50 +0200
Re: 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> - 2016-09-22 18:20 +0200
Re: 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. Darac Marjal <mailinglist@darac.org.uk> - 2016-09-21 16:10 +0200
Page 3 of 3 — ← Prev page 1 2 [3]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2016-09-22 18:20 +0200 |
| Subject | 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. |
| Message-ID | <skeT7-bk-11@gated-at.bofh.it> |
| In reply to | #172656 |
On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote: > A little late, but personally I would have tried using '~/.xprofile' > first. > > I believe the information about this from the Arch Wiki applies equally > to Debian. > > https://wiki.archlinux.org/index.php/xprofile wooledg@wooledg:~$ grep -r xprofile /etc/X11 wooledg@wooledg:~$ Apparently Debian's "X session" is heavily customized, as described in https://www.debian.org/doc/manuals/debian-reference/ch07.en.html#_starting_the_x_window_system Arch's customizations are different and don't appear to be the same as Debian's. What I was missing was a simple pointer from lightdm's joke of a man page to either Xsession(5), with some indication that lightdm *runs* a Debian X session, or directly to the debian-reference web page. At some point I may take a stab at fixing up the wiki page(s) now that we have some actual, useful information. (I should also point out that my Google searches for "debian man lightdm" etc. tended to favor the Debian wiki page, which at this precise moment is just about as useless as the lightdm man page is.)
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-09-22 19:50 +0200 |
| Subject | 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. |
| Message-ID | <skgif-VW-105@gated-at.bofh.it> |
| In reply to | #172660 |
On Thu 22 Sep 2016 at 12:10:35 -0400, Greg Wooledge wrote:
> On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote:
> > A little late, but personally I would have tried using '~/.xprofile'
> > first.
> >
> > I believe the information about this from the Arch Wiki applies equally
> > to Debian.
> >
> > https://wiki.archlinux.org/index.php/xprofile
>
> wooledg@wooledg:~$ grep -r xprofile /etc/X11
> wooledg@wooledg:~$
Good catch! You can have a ~/.xprofile but none of the files in /etc/X11
will look for it. startx uses only the files in /etc/X11; it will ignore
whatever is in such a file.
That does not mean nothing else will look for ~/.xprofile and source it
if it exists. It's one of the wonders of Debian; just when you think you
have a total grasp of the situation something extra comes to light. Time
for some not very onerous detective work. (Clue: DM).
> Apparently Debian's "X session" is heavily customized, as described in
> https://www.debian.org/doc/manuals/debian-reference/ch07.en.html#_starting_the_x_window_system
>
> Arch's customizations are different and don't appear to be the same
> as Debian's.
I'm going to say there is nothing in Arch's setup and documentation
which helps with customising Debian's X. In particular, Debian does not
use ~/.xinitrc. Advice on this file is splattered all over the web and
has lead many a Debian user down a dead end road.
> What I was missing was a simple pointer from lightdm's joke of a man page
> to either Xsession(5), with some indication that lightdm *runs* a Debian
> X session, or directly to the debian-reference web page.
It has to execute an Xsession, either by using the existing one in
/etc/X11 or offering its own. Or a combination of both. Or something
else nobody has mentioned yet.
You could prevent people rolling in the aisles by providing patches for
the manual which would make the situation clearer if your intention is
to improve the documentation. kdm's approach is:
DESCRIPTION
kdm is the KDE display manager also known as login manager. It shows a
graphical login screen for username and password. After authenticating
the user it starts a session.
kdm can be configured for remote login via XDMCP. XDMCP is the "X Dis‐
play Manager Control Protocol" which is used to set up connections
between remote systems over the network.
kdm is a derivative of xdm. man 1 xdm may provide useful information
(requires installed xdm). For X-related problems try man 7x X and man 1
startx.
[toc] | [prev] | [next] | [standalone]
| From | Seeker <seeker5528@comcast.net> |
|---|---|
| Date | 2016-09-23 03:30 +0200 |
| Subject | 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. |
| Message-ID | <skntn-5tp-5@gated-at.bofh.it> |
| In reply to | #172676 |
On 9/22/2016 10:45 AM, Brian wrote: > On Thu 22 Sep 2016 at 12:10:35 -0400, Greg Wooledge wrote: > >> On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote: >>> A little late, but personally I would have tried using '~/.xprofile' >>> first. >>> >>> I believe the information about this from the Arch Wiki applies equally >>> to Debian. >>> >>> https://wiki.archlinux.org/index.php/xprofile >> >> wooledg@wooledg:~$ grep -r xprofile /etc/X11 >> wooledg@wooledg:~$ > > Good catch! You can have a ~/.xprofile but none of the files in /etc/X11 > will look for it. startx uses only the files in /etc/X11; it will ignore > whatever is in such a file. > > That does not mean nothing else will look for ~/.xprofile and source it > if it exists. It's one of the wonders of Debian; just when you think you > have a total grasp of the situation something extra comes to light. Time > for some not very onerous detective work. (Clue: DM). > Way back I used to use '~/.profile'. Somewhere along the way, maybe because I stopped using GDM, that quit working. The indication at that time was it was not a bug and the recommendation seemed to be to use '~/.xprofile'. I'm running unstable by the way. It's been a while since I needed to set variables during login. I do see a '/etc/X11/Xsession.d/60xprofile' file that looks like it should cause '/etc/xprofile' and '~/.xprofile' to get sourced, but that doesn't seem to be happening on my system. I'm using lightdm for my display manager, lxqt for my desktop, with openbox for the window manager most of the time. Will have to look at lxde and kde to see if it is a desktop thing or something else. Later, Seeker
[toc] | [prev] | [next] | [standalone]
| From | Seeker <seeker5528@comcast.net> |
|---|---|
| Date | 2016-09-23 19:10 +0200 |
| Subject | 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. |
| Message-ID | <skC94-6EN-17@gated-at.bofh.it> |
| In reply to | #172694 |
On 9/22/2016 6:18 PM, Seeker wrote: > On 9/22/2016 10:45 AM, Brian wrote: >> On Thu 22 Sep 2016 at 12:10:35 -0400, Greg Wooledge wrote: >> >>> On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote: >>>> A little late, but personally I would have tried using '~/.xprofile' >>>> first. >>>> >>>> I believe the information about this from the Arch Wiki applies equally >>>> to Debian. >>>> >>>> https://wiki.archlinux.org/index.php/xprofile >>> >>> wooledg@wooledg:~$ grep -r xprofile /etc/X11 >>> wooledg@wooledg:~$ >> >> Good catch! You can have a ~/.xprofile but none of the files in /etc/X11 >> will look for it. startx uses only the files in /etc/X11; it will ignore >> whatever is in such a file. >> >> That does not mean nothing else will look for ~/.xprofile and source it >> if it exists. It's one of the wonders of Debian; just when you think you >> have a total grasp of the situation something extra comes to light. Time >> for some not very onerous detective work. (Clue: DM). >> > > Way back I used to use '~/.profile'. Somewhere along the way, maybe > because I stopped using GDM, that quit working. The indication at that > time was it was not a bug and the recommendation seemed to be to use > '~/.xprofile'. > > I'm running unstable by the way. > > It's been a while since I needed to set variables during login. > > I do see a '/etc/X11/Xsession.d/60xprofile' file that looks like it > should cause '/etc/xprofile' and '~/.xprofile' to get sourced, but that > doesn't seem to be happening on my system. > > I'm using lightdm for my display manager, lxqt for my desktop, with > openbox for the window manager most of the time. > > Will have to look at lxde and kde to see if it is a desktop thing or > something else. > > Later, Seeker > > > 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. So it looks like '~/.xsessionrc' is way to go. 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/'? Later, Seeker
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-09-23 19:30 +0200 |
| Subject | 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. |
| Message-ID | <skCsp-6Lq-7@gated-at.bofh.it> |
| In reply to | #172715 |
On Fri 23 Sep 2016 at 10:07:43 -0700, Seeker wrote: > On 9/22/2016 6:18 PM, Seeker wrote: > >On 9/22/2016 10:45 AM, Brian wrote: > >>On Thu 22 Sep 2016 at 12:10:35 -0400, Greg Wooledge wrote: > >> > >>>On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote: > >>>>A little late, but personally I would have tried using '~/.xprofile' > >>>>first. > >>>> > >>>>I believe the information about this from the Arch Wiki applies equally > >>>>to Debian. > >>>> > >>>>https://wiki.archlinux.org/index.php/xprofile > >>> > >>>wooledg@wooledg:~$ grep -r xprofile /etc/X11 > >>>wooledg@wooledg:~$ > >> > >>Good catch! You can have a ~/.xprofile but none of the files in /etc/X11 > >>will look for it. startx uses only the files in /etc/X11; it will ignore > >>whatever is in such a file. > >> > >>That does not mean nothing else will look for ~/.xprofile and source it > >>if it exists. It's one of the wonders of Debian; just when you think you > >>have a total grasp of the situation something extra comes to light. Time > >>for some not very onerous detective work. (Clue: DM). > >> > > > >Way back I used to use '~/.profile'. Somewhere along the way, maybe > >because I stopped using GDM, that quit working. The indication at that > >time was it was not a bug and the recommendation seemed to be to use > >'~/.xprofile'. > > > >I'm running unstable by the way. > > > >It's been a while since I needed to set variables during login. > > > >I do see a '/etc/X11/Xsession.d/60xprofile' file that looks like it > >should cause '/etc/xprofile' and '~/.xprofile' to get sourced, but that > >doesn't seem to be happening on my system. > > > >I'm using lightdm for my display manager, lxqt for my desktop, with > >openbox for the window manager most of the time. > > > >Will have to look at lxde and kde to see if it is a desktop thing or > >something else. > > > >Later, Seeker > > > > > > > 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? > So it looks like '~/.xsessionrc' is way to go. For what? In what circumstance? > 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. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Seeker <seeker5528@comcast.net> |
|---|---|
| Date | 2016-09-24 08:40 +0200 |
| Subject | 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. |
| Message-ID | <skOMV-5Zi-5@gated-at.bofh.it> |
| In reply to | #172717 |
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
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-09-22 21:10 +0200 |
| Subject | Re: 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. |
| Message-ID | <skhxE-1RU-13@gated-at.bofh.it> |
| In reply to | #172637 |
On Thu 22 Sep 2016 at 09:11:53 -0400, Greg Wooledge wrote: > On Wed, Sep 21, 2016 at 09:19:11PM -0500, David Wright wrote: > > > I'm not a DE or DM user, so I'm know very little about them. > > Yes, THIS is the problem! You, and I, and everyone else on the guru side > are just completely stumped. No, the problem is you snipped most of what David Wright said and the essence of his point as I (a non-guru) understood it was lost. So, here it is again: > I'm not a DE or DM user, so I'm know very little about them. But I > don't understand the concept of "user configuration" for a DM. > Wouldn't that be like a user configuring /etc/issue, the login prompt > or /etc/motd ? Logging in on a terminal involves a getty and login prompt. This is not user configurable. You fit in with what is offered or you do not get to log in. It doesn't matter if you have a deep understanding of the process or not. A DM offers the same options of username and password. A user cannot configure that offering in any other way. What's the difference? You might have a legitimate complaint about a DM's documentation but that is a different issue which can be rectified with co-operation between DM developers and users. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-09-22 21:50 +0200 |
| Subject | Re: 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. |
| Message-ID | <skiam-25t-19@gated-at.bofh.it> |
| In reply to | #172637 |
On Thu 22 Sep 2016 at 09:11:53 -0400, Greg Wooledge wrote: > On Wed, Sep 21, 2016 at 09:19:11PM -0500, David Wright wrote: > > But I don't understand the concept of "user configuration" for a DM. > > Wouldn't that be like a user configuring /etc/issue, the login prompt > > or /etc/motd ? > > By user configuration, I mean "which files can the user edit, without > superuser privileges, to alter the behavior of the program". Some of them are listed in the next quoted piece of text. Which ones are not acted on when a DM is used? .xsession? ,xsessionrc? Do you evidence this is not the case? (Forget about .xinitrc. It is an abomination and of no use on Debian). > > Are you perhaps talking about which file, > > like .xsession, .xsessionrc, .Xsession, .xinitrc, etc gets executed > > when you login through the DM? -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Seeker <seeker5528@comcast.net> |
|---|---|
| Date | 2016-09-22 18:20 +0200 |
| Subject | Re: 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. |
| Message-ID | <skeT7-bk-13@gated-at.bofh.it> |
| In reply to | #172599 |
On 9/21/2016 12:07 PM, Anthony Baldwin wrote: > On 09/21/2016 11:05 AM, Greg Wooledge wrote: >> On Wed, Sep 21, 2016 at 10:49:13AM -0400, Tony Baldwin wrote: >>> it seems that I am using lightdm. >> >> I know of absolutely no documentation for configuring lightdm as a >> user. I suspect that the software *has* no user configuration at all, >> because every search I've ever done has come up with nothing. >> >> (For example, https://wiki.debian.org/LightDM has zero instances of >> "home" or "~" or "dot".) > > Oddly this page states, with it's bare face hanging out: > [lightdm] was built as a relatively light-weight and *highly > customizable* alternative to GDM. > Highly customizable is not the same as highly configurable. 3 greeters that customize the lightdm login screen lightdm-gtk-greeter, lightdm-kde-greeter, razorqt-lightdm-greeter. https://packages.debian.org/search?keywords=lightdm+greeter&searchon=names&suite=stable§ion=all Later Seeker
[toc] | [prev] | [next] | [standalone]
| From | Darac Marjal <mailinglist@darac.org.uk> |
|---|---|
| Date | 2016-09-21 16:10 +0200 |
| Subject | Re: 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. |
| Message-ID | <sjQnL-1xc-11@gated-at.bofh.it> |
| In reply to | #172580 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, Sep 21, 2016 at 09:43:15AM -0400, Tony Baldwin wrote: >Greetings, friends, > >I have various scripts in $HOME/bin, many of which I have put in my >.config/openbox/rc.xml so I can fire them off with a keybinding combo, >like ><keybind key="W-b"> > <action name="Execute"> > <startupnotify> > <enabled>true</enabled> > <name>bid</name> > </startupnotify> > <command>bid</command> > </action> > </keybind> > > >(This particular one does cat ~/Documents/bid | xclip -selection c) >bid.txt being a template letter for bidding on translation projects. >I use this to quickly copy the file and then paste it into an e-mail, >then do any relevant edits. >I'my lazy and like to automate things as much as possible where I can >slap a few keys (Alt-m brings up icedove, Ctrl N to compose a new >message, then W-b/Ctrl-v to copy and paste my bid template), >These things used to work perfectly in Wheezy, and even in a previous >Jessie installation, but working in a new Jessie installation, >when I press W-b, and some others I get this: >Failed to execute child process (no such file or directory) >But the script IS in ~/bin/ >$ which bid >/home/tony/bin/bid >and that dir IS in my $PATH: >$ echo $PATH >/home/tony/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games >and it IS executable: >$ ls -la bin/ | grep bid >-rwxr-xr-x 1 tony tony 142 Oct 4 2012 bid >I can execute these scripts from a terminal without any problem but >not via the shortcuts in my rc.xml, nor with grun (shortcut W-r brings >that up fine), nor with dmenu (W-p also working fine) >, and other stuff >Shortuts for stuff in /bin/ or /usr/bin/ (such as for icedove and >iceweasel) seem to work fine, I can lock my screen (W-x engages >slock); it's just my own scripts and stuff in ~/bin that are giving me >trouble.. > >Why? Does the file start with a valid "shebang" line? When you tell some program to run a file "foo", typically what happens is that the program invokes a standard call (Actually, I'm not sure if this behaviour is in the kernel or in libc, either way, it's a "system function") that says "execute this file". Now, if the file is actually executable (e.g. something that you compiled), then you should be good to go, but if it's a script file, then... well the processor doesn't know how to interpret "echo Hello world". However, if the first two characters of the file are "#!" (Pound/octothorpe/hash followed by exclamation-mark/bang... Hash-Bang... haSH-BANG... shebang), then the system identifies this file as a script. The remainder of that line (i.e. everything between the bang and the newline) is taken to be the actual command line to be run. So, that command is run instead and your script is passed to it on stdin. So in summary, a script should start with something like: #!/bin/sh echo hello world It should follow, though, that you don't HAVE to add the shebang line IF you call a proper executable and pass it the name of your script. That is: $ ~/bin/bid # Needs a shebang $ /bin/sh ~/bin/bid # Doesn't need a shebang, but it won't hurt Also, a few final things to be aware of: * Not all programs expand ~ * ~ will expand to the home directory of the calling user (so watch out in cron jobs) * Not all programs bother to search the PATH So, if you're asking a program other than a full shell to execute something for you, it's best to give an absolute path. > >tia, >tony > > > >-- >http://tonybaldwin.me >all tony, all the time > -- For more information, please reread.
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | linux.debian.user
csiph-web