Re: issues with stretch, issue 2 from many
On Tue 27 Nov 2018 at 13:52:25 (+0100), Ionel Mugurel Ciobîcă wrote:
> 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.
Sure. I used fvwm2 explicitly with hamm and slink, maybe even with bo.
But the fact that you still write "2" might indicate that there's
cruft in the system which is doing something unexpected.
> So after the installation, I edit the file $HOME/.xsession
> and I added as last line fvwm2.
I happen not to do it that way; I exec it early in the file so that
it's running while everything else in .xsession comes up. The last
line in .xsession is a wait on the WM's PID.
> I also made the x-window-manager point
> to fvwm2.
I don't understand. Doesn't x-window-manager already point to fvwm2
in /etc/alternatives ?
> When I login the .xsession is not read, like it was done
> before for older releases, but fvwm is started.
Interesting. On my system, ps -ef reveals:
UID PID PPID TIME CMD
david 1495 1297 00:00:00 /bin/sh /usr/bin/X11/startx
david 1517 1495 00:00:00 xinit /etc/X11/xinit/xinitrc -- /etc/X11/xinit/xserverrc :0 vt1 -keeptty -auth /tmp/serverauth.lLPH4nRsUP
david 1518 1517 00:00:33 /usr/lib/xorg/Xorg -nolisten tcp :0 vt1 -keeptty -auth /tmp/serverauth.lLPH4nRsUP
david 1524 1517 00:00:00 /bin/bash /home/david/.xsession
david 1577 1524 00:00:01 /usr/bin/fvwm
so what started yours?
> After many
> 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.
Well, it would if you start both fvwm2 and x-window-manager.
> Question 2.1: Why .xsession is not read and .xsessionrc is read?
Don't know. But you haven't posted how you start X.
> 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.
What sort of error message? I get messages like:
xinit: connection to X server lost
waiting for X server to shut down Server terminated successfully (0). Closing log file.
xinit: unexpected signal 15
but they're expected by me as I either typed Ctrl-Alt-Backspace or shutdown.
> 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 use startx myself. But AIUI Debian has put a lot of effort into
making it possible for X server sessions to end up in the same
configuration whether they were started from a VC or a DM. Your using
.xsessionrc sounds as if you might be working around some other
"misconfiguration" that's happened to work until now. It might even
have been like that since the "Great X Reorganisation" back in the
days of slink.
Cheers,
David.
Reply to: