Hey Forum,

I'm liking the new update, trees are looking good&boot is even more solid if not as solid as ever.

However, I'm having issues described in title. Ive had similar issues, hopefully it is as simple to solve.

Relevant Trees: 
obarunS6# 66-intree -g                    
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->backup db->backup
Contents     : /
               ├─(212,Enabled,classic) tty@ tty12
               ├─(up,Enabled,oneshot) system-hostname
               ├─(up,Enabled,oneshot) mount-run
               ├─(up,Enabled,oneshot) populate-run
               ├─(up,Enabled,oneshot) mount-tmp
               ├─(up,Enabled,oneshot) populate-tmp
               ├─(up,Enabled,oneshot) mount-proc
               ├─(up,Enabled,oneshot) mount-sys
               ├─(up,Enabled,oneshot) populate-sys
               ├─(up,Enabled,oneshot) mount-dev
               ├─(up,Enabled,oneshot) mount-pts
               ├─(up,Enabled,oneshot) mount-shm
               ├─(up,Enabled,oneshot) populate-dev
               ├─(up,Enabled,oneshot) mount-cgroups
               ├─(up,Enabled,bundle) 00
               ├─(up,Enabled,bundle) all-Mount
               ├─(up,Enabled,oneshot) system-hwclock
               ├─(up,Enabled,oneshot) modules-kernel
               ├─(up,Enabled,oneshot) system-random
               ├─(up,Enabled,oneshot) modules-system
               ├─(up,Enabled,oneshot) system-sysctl
               ├─(255,Enabled,longrun) udevd-log
               ├─(432,Enabled,longrun) udevd
               ├─(up,Enabled,oneshot) udevadm
               ├─(up,Enabled,oneshot) system-fontnkey
               ├─(up,Enabled,oneshot) system-fsck
               ├─(up,Enabled,oneshot) mount-fstab
               ├─(up,Enabled,bundle) all-System
               ├─(up,Enabled,oneshot) mount-rw
               ├─(up,Enabled,oneshot) mount-netfs
               ├─(up,Enabled,oneshot) local-loop
               ├─(up,Enabled,oneshot) local-sethostname
               ├─(up,Enabled,oneshot) local-time
               ├─(up,Enabled,oneshot) local-authfiles
               ├─(up,Enabled,oneshot) local-tmpfiles
               ├─(unitialized,Enabled,oneshot) local-rc
               ├─(up,Enabled,oneshot) local-dmesg
               ├─(up,Enabled,bundle) all-Local
               ├─(up,Enabled,oneshot) all-Runtime
               ├─(up,Enabled,bundle) All
               ├─(969,Enabled,longrun) tty-rc@ tty2
               ├─(970,Enabled,longrun) tty-rc@ tty1
               └─(up,Enabled,module) boot@ system

Name         : boot-user
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) setenv@ orb
               ├─(920,Enabled,longrun) svscan@ orb-log
               ├─(944,Enabled,longrun) svscan@ orb
               ├─(up,Enabled,module) scandir@ orb
               ├─(up,Enabled,oneshot) mount-run@ orb
               └─(up,Enabled,module) boot-user@ orb

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(838,Enabled,classic) openntpd-log
               ├─(829,Enabled,classic) cupsd-log
               ├─(832,Enabled,classic) cupsd
               ├─(833,Enabled,classic) wpa_supplicant-log
               ├─(837,Enabled,classic) acpid-log
               ├─(874,Enabled,classic) wpa_supplicant
               ├─(839,Enabled,classic) acpid
               ├─(0,Enabled,classic) openntpd
               ├─(864,Enabled,longrun) consolekit-log
               ├─(865,Enabled,longrun) dbus-log
               ├─(870,Enabled,longrun) dbus
               ├─(883,Enabled,longrun) consolekit
               ├─(863,Enabled,longrun) sddm-log
               ├─(888,Enabled,longrun) sddm
               ├─(866,Enabled,longrun) connmand-log
               └─(884,Enabled,longrun) connmand

% 66-intree -g
Name         : graphics
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : orb
Symlinks     : svc->source db->source
Contents     : /
               ├─(8180,Enabled,longrun) dbus-session@ orb-log
               ├─(1128,Enabled,longrun) pulseaudio-log
               ├─(8079,Enabled,longrun) pulseaudio
               ├─(up,Enabled,oneshot) xdg-user-dirs
               └─(8184,Enabled,longrun) dbus-session@ orb

%  66-inservice dbus-session@ orb
Name                  : dbus-session@ orb
Version               : 0.2.0
In tree               : graphics
Status                : enabled, up (pid 8184) 785 seconds, ready 785 seconds
Type                  : longrun
Description           : dbus session daemon for orb user
Source                : /usr/lib/66/service/dbus-session@ orb
Live                  : /run/66/tree/1003/graphics/servicedirs/dbus-session@ orb
Dependencies          : dbus-session@ orb-log
External dependencies : None
Optional dependencies : None
Start script          : 	execl-subuidgid -o orb
                        	execl-toc -S ${socket_name}
                        	execl-cmdline -s { dbus-daemon ${cmd_args} }
Stop script           : 	execl-subuidgid -o orb
                        	s6-rmrf ${socket_name}
Environment source    : /home/orb/.66/conf/dbus-session@ orb/0.2.0
Environment file      : cmd_args=!--session --print-pid=4 --nofork --nopidfile --address=unix:path=/run/user/${UID}/bus
                        socket_name=!/run/user/${UID}/bus
Log name              : dbus-session@ orb-log
Log destination       : /home/orb/.66/log/dbus-session@ orb
Log file              : 
2020-10-30 23:20:37.358845277  dbus-daemon[1290]: [session uid=1003 pid=1290] Activating service 
2020-10-31 10:21:12.468134132  Gdk-Message: 10:21:12.468: xdg-desktop-portal-gtk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
2020-10-31 10:21:12.468140798  
2020-10-31 10:21:27.443053377  A connection to the bus can't be made
2020-10-31 10:21:27.443847460  
2020-10-31 10:21:27.443853346  (xfconfd:1369): xfconfd-CRITICAL **: 10:21:27.443: Name org.xfce.Xfconf lost on the message dbus, exiting.
2020-10-31 10:21:27.445903524  A connection to the bus can't be made
2020-10-31 10:21:27.463550117  A connection to the bus can't be made
"Dbus session with window manager issues since update"... what issue?
Failed to initialize Xfconf: Could not connect: No such file or directory
maybe Dbus is fine, but how it interacts with Xconf is not.
Check if your run/user/<user_uid>/bus socket is present.
Check the output of the command 
% ck-list-sessions
Please give the output of 
% ls -la ~/.66/conf/svscan@ orb
Also, do you have xfce4 desktop functional or not? This issue appear after the service update or it had be present before?
% ck-list-sessions
Session1:
	unix-user = '1003'
	realname = '(null)'
	seat = 'Seat1'
	session-type = 'unspecified'
	session-class = 'user'
	session-state = 'active'
	active = TRUE
	x11-display = ':0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2020-11-01T04:29:47.171302Z'
	login-session-id = '1'
	XDG_RUNTIME_DIR = '/run/user/1003'
	VTNr = '7'
& 
ls -la ~/.66/conf/svscan@ orb
total 12
drwxr-xr-x 2 orb users 4096 Oct 31 11:58 .
drwxr-xr-x 5 orb users 4096 Oct 31 11:58 ..
-rw-r--r-- 1 orb users  389 Oct 31 23:29 svscan@ orb
No xfce4 desktop, I only use xfce4-power-manager because I haven found out another way to get my brightness function buttons to work on my thinkpad.

I use jwmWM & awesomeWM for zoom because of issues I have with jwm hiding windows after I come from minimized mode rarely.

However the issue for this thread appeared after service update, i dunno if any other packages updated at the same instance contribute to this issue?
take a look if DBUS_SESSION_BUS_ADDRESS is set correctly to DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
i dunno if any other packages updated at the same instance contribute to this issue?
the only one can be the dbus-66serv which is must be version 0.2.0-2 and you need to enable it again(but apparently you already did this) 
% 66-enable -C -F -t graphics dbus-session@ orb

%  echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1003/bus,guid=d032f0f543f3100b7767aff55fa0264e
I put that command in terminal again. No change after reboot except no guid in output of "echo $DBUS_SESSION_BUS_ADDRESS."
Also changed, output of "66-inservice dbus-session@ orb" in terminal shows log file= none.
% 66-inservice dbus-session@ orb
Name                  : dbus-session@ orb
Version               : 0.2.0
In tree               : graphics
Status                : enabled, up (pid 1268) 560 seconds, ready 560 seconds
Type                  : longrun
Description           : dbus session daemon for orb user
Source                : /usr/lib/66/service/dbus-session@ orb
Live                  : /run/66/tree/1003/graphics/servicedirs/dbus-session@ orb
Dependencies          : dbus-session@ orb-log
External dependencies : None
Optional dependencies : None
Start script          : 	execl-subuidgid -o orb
                        	execl-toc -S ${socket_name}
                        	execl-cmdline -s { dbus-daemon ${cmd_args} }
Stop script           : 	execl-subuidgid -o orb
                        	s6-rmrf ${socket_name}
Environment source    : /home/orb/.66/conf/dbus-session@ orb/0.2.0
Environment file      : cmd_args=!--session --print-pid=4 --nofork --nopidfile --address=unix:path=/run/user/${UID}/bus
                        socket_name=!/run/user/${UID}/bus
Log name              : dbus-session@ orb-log
Log destination       : /home/orb/.66/log/dbus-session@ orb
Log file              : None
Just an update, everything seems fine when I use startx command to start. The problem is when I use SDDM to get to WM.
While waiting for Eric take a look at this thread https://www.reddit.com/r/obarun/comments/jnagqb/fresh_install_of_obarun_xfce_first_attempt_to/


What I would do is disable and stop sddm from the $tree it is enabled in
# 66-disable -t $tree -S sddm
then either as root or using sudo start sddm from terminal, and flip back to that tty (tty1??) and see what the output is. It probably throws more detailed messages about what is wrong than that gui label seen on that reddit picture.

I don't know if sddm has options for more verbal messages like sddm -v or sddm -d for debugging ... the more output the closer you get to the problem.

If it makes you feel better I have one friend that I have installed xfce with sddm and another runs lxqt, for a long while, I've done all the updates for them and everything still works fine. I haven't used sddm for at least 3 years now. Just xinit and wm.

EDIT: SDDM should be producing a log as well, maybe /var/log/sddm.log
Good tips fungal_net! I followed those steps and started sddm using "sudo sddm" from tty1 but there was no output in tty1& looking at the log, I cannot see any useful troubleshooting info.

i also tried lxdm with same result so it must be a display manager/greeter trouble with some file
wild shot,
# 66-env boot@ system (or % sudo -E 66-env boot@ system)
change number of ttys to 6
# 66-enable -t boot -F boot@ system
# reboot

sddm has this default of starting on tty7 because most distros have 6 ttys setup 1-6, with having 2 it may be trying to start on 3 and 7 and creates a conflict with X ... maybe... I somehow remember seeing this before. I think it was JM's plasma iso I had tried and sddm was failing and that trick fixed it for me. Or there is somewhere in /etc/sddm.conf that you can specify the tty it wants to run in.
Good shot fungal_net!
... I somehow remember seeing this before. I think it was JM's plasma iso I had tried and sddm was failing and that trick fixed it for me.
That trick fixed it for me, too.
I had mentioned it in some discussion of getting sddm and plasma to work but it was dismissed as irrelevant to the particular problem they were having.

I think x is trying to start on the next non-used tty and sddm tries to start according to its sddm.conf on number 7, so they develop this split personality (or whatever it is called technically) :)
Thank you fungal_net for the link to that reddit post with Eric's solution. That did the trick for me, SDDM had no problem starting, just the Dbus session with window manager.

my $HOME/.xsession file

before 
 # !/usr/bin/bash

list=( $(ls -1 ${HOME}/.66/conf/boot-user) )
for i in ${list[@ ]};do
    var=$(<${HOME}/.66/conf/boot-user/${i})
    for j in ${var[@ ]}; do
		export ${j}
    done
done

66-all up
after 
# !/usr/bin/bash

_user=orb

list=( $(ls -1 /home/${_user}/.66/conf/svscan@ ${_user}) )

for i in ${list[@ ]};do

var=$(</home/${_user}/.66/conf/svscan@ ${_user}/${i})

for j in ${var[@ ]}; do
		export ${j}
    done
done

66-all up
I changed export ${i} from the reddit post to export ${j}...probably matters?
Yes i did a mistake, ${i} must be replaced by ${j}

Powered by Obarun