Greetings professor

What I think happened is that you are doing this months after the transition period. We went from 66 0.3 to 0.4 to 0.5 from May, to June, to early August just so things like this wouldn't happen. And there was a warning back then that you wouldn't be able to upgrade if you skipped the transition. It seems that you upgraded from 0.3 to 0.5.

Now, the best and simplest way to deal with this is to remove the boot tree all together, the other trees, even though 66-intree may appear failing right now, may still work after you have recreated a boot tree. We will see after the first step.

# 66-tree -R boot
# 66-tree -n boot
# 66-enable -t boot boot@ saleem # (or whatever you want to call your boot module)
# 66-env -t boot -e boot@ saleem # (edit your options hostname timez filesystems swap ... etc like you did in the past in boot.conf but now you define here how many ttys you need)
# 66-enable -t boot -F boot@ saleem
# 66-disable -t root tty@ tty1 tty@ tty2 # (or whatever ttys you had enabled in the past - I am just basing this on default from installation)
# 66-intree -zg

reboot and then check your trees, if root and other trees don't work and services are not as they were, you must delete them one by one and recreate new ones (or you may want to use 66-update for root and user and see if it fixes everything up - just don't do this with the old boot still present). Take some time reading the new wiki instructions. In a new installation everything will work without you having to do anything, but to revive an old installation that hasn't been kept current for half a year needs a little work and reading ;)

You can use what is in this wiki, basically starting consolekit dbus and sddm
So maybe make a tree named sddm and enable sddm, dbus and consolekit in it
I don't think you need a user tree and user dbus unless you need some functionality in Openbox that requires such. I don't use them, but I don't use a dm either. I recently tried lxdm and wrote a service for it based on sddm and lightdm -66serv. That worked too.

With xinit you can start openbox without a dm, you need the /etc/X11/Xwrapper need root rights = yes and a .xinitrc in your home directory copy /etc/skel/xinitrc into ~/,xinitrc

Can you print out the output of
% sudo 66-intree -g
% 66-intree -g

There seem more things not running than nm

2021-01-05 17:59:06.112783691  e2fsck: Cannot continue, aborting.

What do you get when you try

% sudo mount -a

(0,Enabled,classic) tty@ -tty1

# 66-disable -t root -S tty@ -tty1

remove the boot-user tree that is broken

# 66-tree -R boot-user

and remake one

# 66-tree -nE boot-user

follow all the instructions on wiki https://wiki.obarun.org/doku.php?id=dbus_and_dm

just replace the oblive with your username

Don't forget to make a user tree as well and enable dbus

What do you need 10 ttys for :) Poor X server only has tty11 to work on

Is it the same after reboot?

As user

% 66-intree -g
% 66-enable -v4 -t usertreename  -S dbus-session@ saleem

What is the output?

If you have no user tree create one, make it current and enable it (66-tree -ncE usertreename) I think the default with obarun installation for xfce or kde/plasma is graphics, maybe jwm as well, but if you have no tree or no current tree enabling a service without a -t will not work. If one exists and is current, and your boot-user tree is functional, then there shouldn't be a problem.

If you have a user tree that you create with 66-tree -n usertreename it needs to be current and enabled, so

66-tree -cE usertreename

if you don't have any user trees then

66-tree -ncE usertreename

Are you sure you have made a complete update and everything is current? (pacman -Suy)

We are starting from scratch again, I can't assume what the current status is and how it relates to output from 04-05/1

|-(0,Enabled,classic) tty@ -tty1
You have a tty@ -tty1 enabled in root? # 66-disable -t root -S tty@ -tty1

Edit /etc/66/init.conf and change verbosity=4 reboot and /run/66/log/current should be a detailed log of anything that happens during boot. What happens with the next enabled tree will not show, but if everything is good with boot then you can log in and use 66-intree and 66-inservice to diagnose each tree and service analytically.

The log for X is at /var/log/Xorg.0.log

# cat  /var/log/Xorg.0.log | grep "(EE)"

This will only show lines from the log that have errors, the first error is what is important

Now you have sddm enabled still, or not? If sddm was working you would see the console login screen temporarily and then sddm would kick in and take you to a graphic display to login. I was asking about updates because there was some brief time that sddm had a problem and that was fixed. So I am working on the assumption your system is current (upgraded).

If you have sddm disabled now, there are two things you need to have to startx or xinit. /etc/X11/Xwrapper.config with contents:

# /etc/X11/Xwrapper.config
needs_root_rights = yes

have a .xinitrc that ends with either command:

# exec ck-launch-session openbox-session
exec openbox-session

without consolekit running

exec ck-launch-session openbox-session
# exec openbox-session

with consolekit running (I simply leave the # comment in there so you can switch depending on what you need running or not - easier than typing a different command)

Make sure other commands are disabled. (lines that begin with exec or cmd)
Your openbox should start

You can also boot with an obarun live JWM image and from terminal mount the partition (I believe I see it is /dev/sda10 --> sudo mount /dev/sda10 /mnt --> sudo arch-chroot /mnt ) and make changes to your system, but since you get to console you should try and do the repairs from console.

If you run most console commands you can follow them with a >/tmp/log and it will send the output to a file named /tmp/log
If you want to append to that file you use >>
so as user:

% sudo 66-intree -g >/tmp/66tree 
% 66-intree -g >>/tmp/66tree 

Will write the output to /tmp/66tree
first for root then for user.

One correction on my part
sudo 66-intree -g >/tmp/66tree
-z if for color, -g is for graphical analytical information (I am correcting the above message as to not confuse other users)

But you can't run this from chroot, this is why all services are dead because you are running them from a system without s6/66 Even if you did run it from live obarun it would show the services that match between trees and the live image.
So never chroot and go by what 66-intree/service shows, it is wrong.

Also, do me a favor (wild shot - you can do this from chroot no sudo needed since you are root) do:

sudo -E 66-env -t boot -e boot@ saleem
go to tty#  and just use 6 instead of 10
sudo 66-enable -t boot -F boot@ saleem
reboot  (or exit chroot and reboot)

This is the log for the boot process, which seems all great.
The 66-intree -g (root and user) is what I would like to see
Also see what this says:

% sudo 66-inservice -p20 sddm