Re: issues with stretch, issue 2 from many
- Date: Fri, 30 Nov 2018 16:20:15 +0100
- From: Ionel Mugurel Ciobîcă <I.M.Ciobica@xxxxxxxxx>
- Subject: Re: issues with stretch, issue 2 from many
On 27-11-2018, at 13h 52'25", Ionel Mugurel Ciobîcă wrote about "issues with stretch, issue 2 from many"
> Dear all,
> I have issues with stretch, to many to count...
> This one will focus on the window manager startup.
> 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
@ Brian, here is my formal .xsession (currently .xsessionrc) file:
rclock -fg white -bg black -fn
eval `ssh-agent -s`
xrdb -m .Xresources
xrdb -m .Xdefaults
setroot -solid steelblue1
( sleep 2 ; /home/mugurel/bin/*ncepe ) &
startx would have been bringing up whatever x-window-manager was
pointing at, which was kde.
xsession was not read because I did not get the clock, I was not asked
for the passphrase, I did not get the background, etc.
I am not abusing anything. .xsession was working before stretch and it
is not working with stretch. Reading some manuals I found out about
.xsessionrc, so I renamed .xsession into .xsessionrc.
I am not fun of startx, it will read my .xsession?
@ David, before login in the first time as user, after installation, I
check if the executable fvwm2 exists. See this:
~> ls -ltr /usr/bin/fvwm2 /usr/bin/fvwm /etc/alternatives/fvwm
-rwxr-xr-x 1 root root 908056 ian 16 2017 /usr/bin/fvwm2
lrwxrwxrwx 1 root root 22 oct 18 09:35 /usr/bin/fvwm -> /etc/alternatives/fvwm
lrwxrwxrwx 1 root root 14 oct 18 09:35 /etc/alternatives/fvwm -> /usr/bin/fvwm2
So, yes, the executable is fvwm2. It was always fvwm2.
If your call to fvwm2 is first in .xsession, how do you get the rest
to be executed?
Initial x-window-manager was pointing to kde.
My fvwm2 is started by .xsession. The second instance is started by
something that died, because the parent is now init. I do not start
both fvwm2 and x-session-manager. Something (that I try to find out by
asking the list, see question 2.2) is starting it. I want to stop that
behaviour. Which is only happening on stretch.
I use xdm.
@ Greg: I do not switching things around randomly and frequently. I
use xdm. I tried kdm when I encounter the issues with .xsession not
As I already posted:
1. I use latest Debian stable. Fresh install.
2. I use xdm to login.
3. X starts automatically
About 2, is not that hard. I usually uninstall all alternative dm's and
then install xdm, before I login the first time as user.
I do not use gnome. I uninstall all packages related to gnome.
Any (new) ideas what I can do?