session startup step-thru

yair · 2018-01-19 14:21:50

i've been using arch for over a year now, love it.

but ever since some issue with TeamViewer that seems only to be solved by setting up a display manager i have lost grasp of my session startup script order.

let me explain

before i had my session managed by .xintirc with exec i3 at its end.
now i've installed lightDM which is run by systemd and ever since i cant figure out what scripts are running when i reboot my pc.

what is the best way to track what (and in what order) is loading when i reboot?
sort of debug step thru of the process.

hope i am making sense

Last edited by yair (2018-01-19 14:24:46)

Slithery · 2018-01-19 14:33:07

You could always do...
https://wiki.archlinux.org/index.php/Di … _a_session

For what happens when launching your current i3 session look at...
/usr/share/xsessions/i3.desktop

yair · 2018-01-19 14:41:24

/usr/share/xsessions/i3.desktop
is just a call to exec i3, but what scripts are in the way?
like my ssh-agent, should be handeld by .zshrc, who is calling zshrc?

isnt there a way to actually see the steps?

and setting xinitrc using lightdm is giving me weird results, like it's not respecting auto login to user .

i want more logs...

ooo · 2018-01-19 15:01:35

you could use pstree to check which processes are started by lightDM or the session you choose on login.

yair · 2018-01-19 15:12:13

relevent (?) pstree output:

├─i3bar(1110)───py3status(1135)─┬─i3status(1188)
│ ├─{py3status}(1187)
│ ├─{py3status}(1191)
│ └─{py3status}(1192)
├─lightdm(602)─┬─Xorg(728)─┬─{Xorg}(752)
│ │ └─{Xorg}(779)
│ ├─lightdm(831)─┬─i3(1087)
│ │ ├─{lightdm}(1069)
│ │ └─{lightdm}(1072)
│ ├─{lightdm}(603)
│ └─{lightdm}(605)

what can i make out of this?

Slithery · 2018-01-19 15:28:22

https://wiki.archlinux.org/index.php/Di … tostarting

Also check /etc/lightdm/Xsession

Last edited by Slithery (2018-01-19 15:29:32)

yair · 2018-01-19 15:37:45

been there, removed xprofile and the only thing relevant in xinitrc.d is that one, which i cant decypher.

➜  xinitrc.d ls
40-libcanberra-gtk-module.sh  50-systemd-user.sh
➜  xinitrc.d cat 50-systemd-user.sh 
#!/bin/sh

systemctl --user import-environment DISPLAY XAUTHORITY

if which dbus-update-activation-environment >/dev/null 2>&1; then
        dbus-update-activation-environment DISPLAY XAUTHORITY
fi

returning to my original question, is it impossible to step thru the sequence?

thanks for the help guys

yair · 2018-01-19 19:09:26

so i tried to solve my issue with inability to autologin to a session using xinitrc. https://wiki.archlinux.org/index.php/Di … tostarting

what happens now is after reboot i get to the greeter and not to i3wm, as expected

i looked at the ligthdm log at /var/log/lightdm/lightdm.log
here are two logs, the right one is a copy when it reached the greeter,
the left is after i entered my user\password in the greeter
and arrived at my destination, i3wm

https://www.diffchecker.com/UsrgRCGI

cat /etc/lightdm/lightdm.conf

[LightDM]
run-directory=/run/lightdm

[Seat:*]
session-wrapper=/etc/lightdm/Xsession
autologin-user=yair
autologin-session=xinitrc

cat ~/.xinitrc

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then

    xrdb -merge $sysresources

fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then


    xrdb -merge "$userresources"

fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

#exec i3
#log terminal output
exec i3 -V >> ~/log/i3log-$(date +'%F-%k-%M-%S') 2>&1

yair · 2018-01-19 19:33:20

regarding line 19 on the lightdm.log

	[+0.16s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)

i don't want to install it as it can mess startup ,judging by comments in the AUR ,and it seems just eyecandy

hdante commented on 2017-11-27 01:26			 
Hello, I can confirm the problem with gdm-plymouth.service, when used, it breaks systemd startup with the message "A start job is running for Hold until boot process finishes up", blocking gettys and cosole logins

Arch Linux

#1 2018-01-19 14:21:50

session startup step-thru

#2 2018-01-19 14:33:07

Re: session startup step-thru

#3 2018-01-19 14:41:24

Re: session startup step-thru

#4 2018-01-19 15:01:35

Re: session startup step-thru

#5 2018-01-19 15:12:13

Re: session startup step-thru

#6 2018-01-19 15:28:22

Re: session startup step-thru

#7 2018-01-19 15:37:45

Re: session startup step-thru

#8 2018-01-19 19:09:26

Re: session startup step-thru

#9 2018-01-19 19:33:20

Re: session startup step-thru

Board footer