Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #172822
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | linux.debian.user |
| 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. |
| Date | 2016-09-26 23:50 +0200 |
| Message-ID | <slLWF-Gc-5@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <skiDo-2wz-5@gated-at.bofh.it> <skBG1-6fB-1@gated-at.bofh.it> <sl0XL-53s-1@gated-at.bofh.it> <sllSx-1a9-1@gated-at.bofh.it> <slLtE-wZ-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Sep 26, 2016 at 10:19:27PM +0100, Brian wrote: > But now we have > > > User configuration may be done in a few different ways. The simplest > > way is to create a ~/.xsessionrc file,..... > > The pedantic side of me asks - why is it the simplest way? And in what > cirumstances? Because it's *additive*. It's just some stuff that happens in addition to the system launching your default WM/DE, and whatever else the system does by default (setting up an ssh-agent? I don't even know). You don't have to do all of those things yourself. Just counting lines of code in the most ridiculously oversimplified cse, it should be obvious that PATH=~/bin:$PATH is simpler than PATH=~/bin:$PATH exec x-session-manager Two is more than one. > > Finally, note that the ~/.xsession file is only read if you > > are using a Debian X session. If you login with gdm3 and > > choose a GNOME session, the ~/.xsession file will be ignored > > completely. (But you may still use ~/.xsessionrc.) > > Not observed in testing. /etc/gdm3/Xsession also has a stanza beginning > "SESSIONFILES=$(run_parts $(SYSSESSIONDIR)" which also appears to > contradict this statement. SYSSESSIONDIR is /etc/X11/Xsession.d. If I've made factual errors, please correct them. I'm trying my best to piece together how gdm3 works based on the existing documentation (written by Overfiend over a decade ago), and other, older wiki pages which may themselves be incorrect, and my extremely limited past knowledge of gdm. Note that I do not *use* gdm3 myself, nor lightdm, nor xdm, or any other display manager, but I did briefly experiment with gdm many years back. I leave you with this (perhaps) amusing excerpt from a ~/.xsession file, a remnant of those experimental days. Make of this what you will. ========================================================================= # If we're running under gdm, then we do *not* want gnome-session to be # spawned when this script exits. I learned this hack by reading the # /etc/gdm/Sessions/Gnome file (IIRC). DEBUG_GNOME_SESSION='Let me the hell out!' ========================================================================= Back then, under gdm, if you had an .xsession file, it would be read, but then after you exited from your chosen window manager, you'd get GNOME! Or at least that's how I remember it. And setting this shell variable caused that not to happen. And it was all completely undocumented, because why would a user with gdm installed ever want anything *other* than GNOME?
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web