Thursday, August 2, 2018

When you're login is borked

Using lxdm as login manager for entering an openbox desktop environment, I was rather surprised I suddenly experienced a halt halfway starting up.
This was years ago something like that happened.
First I checked if the hard drive by entering another installation on that particular hard drive; that was OK so HD was not damaged.

Another boot into Archbang led to the same failure to get to see lxdm doing, what it is suppose to do.

Using ctl+alt+f2 I was able to start another terminal session, tty2.
Loging  in as user and giving password  I was able to start openbox by using:
startx

I couldn't discover what was wrong with lxdm and decided to check .xinitrc in /user/home/
Was OK with rule
exec openbox-session
Now checking ~/.bash_profile 
making sure following rule was active:
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx 

As alternative to lxdm I decided to choose to autologin using systemd

Commands:

cp /usr/lib/systemd/system/getty@.service /etc/systemd/system/autologin@.service

Symbolic linking:
ln -s /etc/systemd/system/autologin@.service /etc/systemd/system/getty.target.wants/getty@tty1.service

If the link is already active you can edit getty@tty1.service in /etc/systemd/system/getty.target.wants
by changing
ExecStart=-/sbin/agetty -o '-p -- \\u' --noclear %I $TERM
to in my case
ExecStart=-/sbin/agetty -a paul %I 38400

Reload daemon:
systemctl daemon-reload

And restart service:
systemctl start getty@tty1.service

Wednesday, August 1, 2018

howto use setup.py file

sudo ./setup.py install

Blog Archive