> Most importantly you are not starting up a window manager there!?
> Which is the whole point of the ~/.xsession file. You may find
> reading through the default startup scripts /etc/X11/Xsession* useful
> to understand this process. The very last line is 'exec $STARTUP'.
> The 'exec' overlays a
> I had this problem for months with one box.
...
> Perhaps yours is that easy too.
nope, the shell is set correctly.
[EMAIL PROTECTED] acs]$ grep acs /etc/passwd
acs:x:1000:1000:Adam Siepel,,,:/home/acs:/bin/bash
> Make sure your ~/.xsession file is executable.
>
> chmod
> How X starts up can be a mystery. I use "startx" which uses my
> ~/.xsession. Others do the same and report ~/.xsession is ignored in
> favour of ~/.xinitrc.
>
> With that in mind, change the file in question. The first line should
> be:
>
> #!/bin/bash --login
>
> which will make it a lo
on in the way,
allow-user-xsession in Xsession.options, etc.).
Just to be clear, the basic symptom is that variables set in .bash_profile
(including my path) are undefined/incorrect in all applications, including
terminals. Setting them in ~/.xsession, or sourcing .bash_profile from
~/.xsession doesn
4 matches
Mail list logo
