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.
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: 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
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.
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.
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.
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
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.
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
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.
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.
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.
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.)
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.
On 9/22/2016 8:25 AM, Tony Baldwin wrote: On 09/22/2016 10:15 AM, Tixy wrote: On Thu, 2016-09-22 at 09:11 -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". Are you perhaps talking about which file, like .xsession, .xsessionrc, .Xsession, .xinitrc, etc gets executed when you login through the DM? Yes, precisely this question. What can an end user, who uses one of the various display managers and desktop environments in Debian, do to configure their own environment? I edit ~/.xsessionrc to have a single line: . /home/tixy/.profile Which makes X sessions include the same profile as standard login shells. And my .profile has (or I added?) # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi Thank you, Tixy, This worked perfectly. I created the .xsessionrc file (didn't previously have one), and found that my .proile already had the needed part in it (possibly because I'd already added the same to my .bashrc ?) Logged out and back in, and now my keybinding are working to fire off my scripts. such as this one, which I fire off qwith the print screen key: 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 Later, Seeker
