Re: issues with stretch, issue 2 from many
On Tue 27 Nov 2018 at 13:52:25 +0100, Ionel Mugurel Ciobîcă wrote:
> Dear all,
>
> I have issues with stretch, to many to count...
> This one will focus on the window manager startup.
>
> I did a fresh install of Debian stretch using net install disk.
> I use Debian (and Linux) from 1997. In all this time I used fvwm2 as
> windows manager. I also used Unix in 1995-1996 with fvwm2.
>
> So after the installation, I edit the file $HOME/.xsession
> and I added as last line fvwm2.
You could show us your .xsession.
> I also made the x-window-manager point
> to fvwm2.
That should have been done for you. startx should (without .xsession}
bring up fvwm.
> When I login the .xsession is not read, like it was done
> before for older releases, but fvwm is started. After many
How do you know it is not read? (That's a different question from asking
why it was not acted on).
> permutations I found out that if I rename the .xsession into
> .xsessionrc then the file is read, but then the fvwm is started twice,
> one after each other. In other words after I exit fvwm it will enter
> again in fvwm, but the second time without the ssh-agent and other
> things.
Xsession(5) describes what .xsessionrc is used for. Does your use fit
the intended use? Or are you abusing the file's intended purpose?
> Question 2.1: Why .xsession is not read and .xsessionrc is read?
> Question 2.2: Who starts the second call of fvwm? If I comment out the
> fvwm call in .xsession(rc) then the fvwm doesn't use the ssh-agent
> (for example). At the moment I simply deleted x-window-manager, so
> when I logout from fvwm I get a error/warning instead of a new fvwm
> session.
>
> I tried both kdm and xdm as display managers. It will make no
> difference. I use fvwm 2.6.7. I have Linux 4.9.0-8-amd64.
>
> I would appreciate any hint.
Make it simple to begin with. Type startx (no .xsession) and go from
there when you have that working.
--
Brian.
Reply to: