z@ obarunS6 ~ % 66-start -v4 pulseaudio 
66-start(src/lib66/ssexec_start.c: ssexec_start(): 247): fatal: scandir: /run/66/scandir/1002 is not running: No such file or directory

z@ obarunS6 [111] ~ % 66-intree

Name         : base
Initialized  : no
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : z
Symlinks     : svc->source db->backup
Contents     : pulseaudio-log pulseaudio dbus-session@ z-log dbus-session@ z
so the needed dir seems to be in /run/user/1002

i tried reinstall pulseaudio-66serv, 66-update etc.
but seems to have a old pulse serv script somewhere or something
how do i fix this, please?


ps: i can start it with success via dbus-launch pulsaudio however
First 66-update is no longer mandatory at upgrade time. You have nothing to do.

Please share the ouptut of 
% sudo 66-intree -g
% 66-intree -g
% ls -la /home
The idea here for why Eric is asking to provide the output is first (I think) the output for base: 
Name         : base
Initialized  : no
Enabled      : yes
Although base is enabled is not starting, and why is also indicated by trying to start pulseaudio, as a user when a /run scandir is not set up by root for the user. So you go one level higher, which is the tree usually labeled as boot-user. Why is it not working?

There may be several reasons (you may want to take a look at the current thread about consoletracker - I am trying to digest this myself) but it may be as simple as starting boot-user after another tree that for some reason is disabled, or deactivated. The contents of the home directory will show the name and rights to your user's home directory.

Also, since you are user xxx (1002) that indicates that two other users were previously existing in the system, 1000, and 1001. Normally, manually you can create the first user be 6858.

Let's say you create a user named buba, then a user named boba, then delete, buba, then create a new buba, that will be buba 1002. If the boot-user tree was setup originally for buba:1000 and now you are loging in as buba:1002 the scandir is made for 1000 and there is none at 1002. So ls -lh /run/66/scandir or /run/66/log should have 0 for root and user codes for user scandir.

At least this is my interpretation of why Eric is asking you for this output, but trying to develop and share skills of troubleshooting myself.

Scandir, like runsvdir in runit, is a directory where service definition and database is thrown at s6 to run and supervise.
It is like a meat grinder, you throw stuff on it and it grinds it and spits it out.
obarunS6# sudo 66-intree -g
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(180,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,oneshot) system-hwclock
               ├─(up,Enabled,oneshot) modules-kernel
               ├─(up,Enabled,oneshot) system-random
               ├─(up,Enabled,oneshot) modules-system
               ├─(up,Enabled,oneshot) system-sysctl
               ├─(227,Enabled,longrun) udevd-log
               ├─(398,Enabled,longrun) udevd
               ├─(up,Enabled,oneshot) udevadm
               ├─(up,Enabled,oneshot) system-fontnkey
               ├─(up,Enabled,bundle) all-Mount
               ├─(up,Enabled,oneshot) system-fsck
               ├─(up,Enabled,oneshot) mount-fstab
               ├─(up,Enabled,bundle) all-System
               ├─(up,Enabled,oneshot) mount-rw
               ├─(up,Enabled,oneshot) local-loop
               ├─(up,Enabled,oneshot) local-sethostname
               ├─(up,Enabled,oneshot) local-time
               ├─(up,Enabled,oneshot) local-tmpfiles
               ├─(up,Enabled,oneshot) local-authfiles
               ├─(up,Enabled,oneshot) local-dmesg
               ├─(up,Enabled,oneshot) mount-netfs
               ├─(up,Enabled,bundle) all-Local
               ├─(up,Enabled,oneshot) all-Runtime
               ├─(up,Enabled,bundle) All
               ├─(876,Enabled,longrun) tty-rc@ tty2
               ├─(1075,Enabled,longrun) tty-rc@ tty1
               └─(up,Enabled,module) boot@ system

Name         : boot-user
Initialized  : no
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->backup
Contents     : /
               ├─(unitialized,Enabled,oneshot) setenv@ z
               ├─(0,Enabled,longrun) svscan@ z-log
               ├─(0,Enabled,longrun) svscan@ z
               ├─(unitialized,Enabled,module) scandir@ z
               ├─(unitialized,Enabled,oneshot) mount-run@ z
               └─(unitialized,Enabled,module) boot-user@ z

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(680,Enabled,classic) wpa_supplicant-log
               ├─(0,Enabled,classic) wpa_supplicant
               ├─(684,Enabled,classic) dhcpcd-log
               ├─(690,Enabled,classic) dhcpcd
               ├─(688,Enabled,classic) cupsd-log
               ├─(692,Enabled,classic) bluetoothd-log
               ├─(827,Enabled,classic) bluetoothd
               ├─(689,Enabled,classic) cupsd
               ├─(down,Enabled,oneshot) mount-run-z
               ├─(down,Enabled,oneshot) setenv-z
               ├─(719,Enabled,longrun) scandir-z-log
               ├─(0,Enabled,longrun) scandir-z
               ├─(down,Enabled,bundle) All-z
               ├─(724,Enabled,longrun) dbus-log
               ├─(744,Enabled,longrun) dbus
               ├─(733,Enabled,longrun) connmand-log
               ├─(789,Enabled,longrun) connmand
               ├─(734,Enabled,longrun) consolekit-log
               └─(788,Enabled,longrun) consolekit

z@ obarunS6 [111] ~ % 66-intree

Name         : base
Initialized  : no
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : z
Symlinks     : svc->source db->backup
Contents     : pulseaudio-log pulseaudio dbus-session@ z-log dbus-session@ z


z@ obarunS6 [111] ~ % ls -la /home
total 16G
drwxr-xr-x  11 root   root   4.0K Jun 13  2020 ./
drwxr-xr-x  21 root   root   4.0K Feb 15 08:27 ../
drwx------  13 a      a      4.0K Nov  7  2019 a/
drwx------  22 oblive oblive 4.0K Jul  5  2019 oblive/
drwx------  15 rz     rz     4.0K Jun 15  2020 rz/
drwx------  16 t      t      4.0K Jun  5  2020 t/
drwx------ 114 z      users   12K Feb 19 00:40 z/
ah, ok my group is users migrated from an old installation. might chown -R z:z help?
The question is whether z is your 1002 user, ( cat /etc/group | grep 1002 )

But the primary problem you have is that boot-user is not enabled
Name         : boot-user
Initialized  : no
Enabled      : no

# 66-tree -E boot-user
# 66-tree -S root boot-user
This enables boot-user and starts it after root, since dbus and ck are active there.
Also, you will have a conflict between the boot-user@ z from your boot-user tree and the services All-z, scandir-z, setenv-z and mount-run-z from your root tree.
So apply what @ fungalnet said AND disable the old service from you root tree: 
% sudo 66-disable -t root All-z scandir-z setenv-z mount-run-z
then reboot.
:(, now nothing works.

/run/66/log/0/current writes:
2021-02-20 09:32:54.658532974  s6-rc: info: service svscan@ z-log: starting
2021-02-20 09:32:54.664603135  s6-rc: info: service svscan@ z-log successfully started
2021-02-20 09:32:54.665132716  s6-rc: info: service mount-run@ z successfully started
2021-02-20 09:32:54.687316997  s6-rc: info: service setenv@ z successfully started
2021-02-20 09:32:54.687443244  s6-rc: info: service svscan@ z: starting
2021-02-20 09:32:57.689170416  s6-svlisten1: fatal: timed out
2021-02-20 09:32:57.690458431  s6-rc: warning: unable to start service svscan@ z: command exited 99
2021-02-20 09:32:57.690619719  66-all(src/lib66/ssexec_dbctl.c: ssexec_dbctl(): 349): fatal: unable to start services selection
2021-02-20 09:32:57.691837858  all-Runtime: fatal: crashed! -- Your machine is operational but some runtime service failed to start correctly. Please see the complete boot log at /run/66/log/0/current for further information.
ps:
i am pretty sure z was/is my 1002 user. but for some reason it was deleted from group and shadow file, so i readded it. but without result.
please post again the output of: 
% sudo 66-intree -g
% 66-intree -g
and the output of 
pacman -Qs 66

obarunS6# 66-intree -g
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(188,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,oneshot) system-hwclock
               ├─(up,Enabled,oneshot) modules-kernel
               ├─(up,Enabled,oneshot) system-random
               ├─(up,Enabled,oneshot) modules-system
               ├─(up,Enabled,oneshot) system-sysctl
               ├─(230,Enabled,longrun) udevd-log
               ├─(406,Enabled,longrun) udevd
               ├─(up,Enabled,oneshot) udevadm
               ├─(up,Enabled,oneshot) system-fontnkey
               ├─(up,Enabled,bundle) all-Mount
               ├─(up,Enabled,oneshot) system-fsck
               ├─(up,Enabled,oneshot) mount-fstab
               ├─(up,Enabled,bundle) all-System
               ├─(up,Enabled,oneshot) mount-rw
               ├─(up,Enabled,oneshot) local-loop
               ├─(up,Enabled,oneshot) local-sethostname
               ├─(up,Enabled,oneshot) local-time
               ├─(up,Enabled,oneshot) local-tmpfiles
               ├─(up,Enabled,oneshot) local-authfiles
               ├─(up,Enabled,oneshot) local-dmesg
               ├─(up,Enabled,oneshot) mount-netfs
               ├─(up,Enabled,bundle) all-Local
               ├─(up,Enabled,oneshot) all-Runtime
               ├─(up,Enabled,bundle) All
               ├─(870,Enabled,longrun) tty-rc@ tty2
               ├─(871,Enabled,longrun) tty-rc@ tty1
               └─(up,Enabled,module) boot@ system

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(674,Enabled,classic) wpa_supplicant-log
               ├─(0,Enabled,classic) wpa_supplicant
               ├─(675,Enabled,classic) dhcpcd-log
               ├─(677,Enabled,classic) dhcpcd
               ├─(685,Enabled,classic) cupsd-log
               ├─(680,Enabled,classic) bluetoothd-log
               ├─(826,Enabled,classic) bluetoothd
               ├─(684,Enabled,classic) cupsd
               ├─(707,Enabled,longrun) dbus-log
               ├─(717,Enabled,longrun) dbus
               ├─(711,Enabled,longrun) connmand-log
               ├─(736,Enabled,longrun) connmand
               ├─(708,Enabled,longrun) consolekit-log
               └─(735,Enabled,longrun) consolekit

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



z@ obarunS6 chromium % 66-intree -g
Name         : base
Initialized  : no
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : z
Symlinks     : svc->source db->source
Contents     : /
               ├─(0,Enabled,longrun) pulseaudio-log
               ├─(0,Enabled,longrun) pulseaudio
               ├─(0,Enabled,longrun) dbus-session@ z-log
               └─(0,Enabled,longrun) dbus-session@ z


obarunS6# pacman -Qs 66
local/66 0.6.1.1-1 (base s6-suite)
    small tools built around s6 and s6-rc programs
local/66-tools 0.0.7.1-1 (base s6-suite)
    small tools and helpers for service scripts execution
local/bluetoothd-66serv 0.2.2-1
    bluetoothd service for 66 tools
local/boot-user@ -66serv 0.4.2-1
    Set of service to create a nested user scandir with console tracker and display manager support
local/boot@ -66serv 2.3.0-1 (base s6-suite)
    Complete and portable set of services to properly boot a machine with 66 tools
local/connmand-66serv 0.2.0-1
    connmand service for 66 tools
local/consolekit-66serv 0.2.0-1
    consolekit service for 66 tools
local/cupsd-66serv 0.2.0-1
    cupsd service for 66 tools
local/dbus-66serv 0.2.0-2
    dbus service for 66 tools
local/dhcpcd-66serv 0.2.0-1
    dhcpcd service for 66 tools
local/dmraid-66serv 0.2.0-1
    dmraid service for 66 tools
local/haveged-66serv 0.2.0-1
    haveged service for 66 tools
local/ntpd-66serv 0.2.0-1
    ntpd service for 66 tools
local/pulseaudio-66serv 0.2.0-1
    pulseaudio service for 66 tools
local/root-66tree 0.1.2-1
    create a tree for 66 tools named root with tty1 tty2 enabled by default
local/scandir@ -66serv 0.3.0-1
    Service to create a nested user scandir
local/sddm-66serv 0.2.1-1
    sddm service for 66 tools
local/tty@ -66serv 0.2.0-1
    tty@  service for 66 tools
local/wpa_supplicant-66serv 0.2.0-1
    wpa_supplicant services for 66 tools
local/xdg-user-dirs-66serv 0.2.1-1
    xdg-user-dirs service for 66 tools
sometimes, not always, # grpck shows any problems with users/groups
/var/log/66/svscan@ z/current

contains just

2021-02-20 12:15:57.163549028 66-scandir: usage: 66-scandir [ -h ] [ -z ] [ -v verbosity ] [ -l live ] [ -b|B ] [ -c ] [ -L log_user ] [ -s skel ] [ -o owner ] create|remove
2021-02-20 12:15:58.162461475 66-scandir: usage: 66-scandir [ -h ] [ -z ] [ -v verbosity ] [ -l live ] [ -b|B ] [ -c ] [ -L log_user ] [ -s skel ] [ -o owner ] create|remove
2021-02-20 12:15:59.163282894 66-scandir: usage: 66-scandir [ -h ] [ -z ] [ -v verbosity ] [ -l live ] [ -b|B ] [ -c ] [ -L log_user ] [ -s skel ] [ -o owner ] create|remove

maybe 66-scandir gets called with wrong switches?
apperently i had to

66-enable -t boot-user boot-user@ z

now its working. except i get XDG_RUNTIME_DIR not found
so i have to manually export XDG_RUNTIME_DIR =/run/user/1002 to get my dbus running

...the days i had to invest as a linux noob to hav this 66 contraption working again and again ...
Next time try: 66-enable -t boot-user -SF boot-user@ z

-F passes any changes you made to the .conf through 66-env to the active module and -S starts the module. If it is not started manually then you have to wait for next reboot for the user scandir to be created.
With any service or module, if you want to enable it and start it right away you have to use the -S option.
If the tree is -E(enabled 66-tree -E treename ) it tries to start after boot, in the order you specify among other Enabled trees. Once the tree is initialized all services/modules in the tree try to start.

If you wanted to reduce the system to be as simple as a runit, openrc, sysvinit, you can have to boot tree (which other systems don't let you touch or configure, it is usually part of their init-rc set) you can have just one other tree where everything can be thrown in. Some services will race each other and fail and restart to finally come to a stable state, like ntpd will not work until network is up and running, and boot-user@ z can be added in that one tree. Call it root or call it zoot it doesn't matter, as long as you create is as (66-tree -ncE zoot). To split different things in trees is a luxury 66 gives you. Somethings you don't always need running all the time, some you need only for specific work. Like a docker tree to run a docker image, 66-tree -n docker. You need to run docker tree services "66-all -t docker up" then you finish you type the same command with up switched to down, the tree is down and services stop.

Once you get the hang of it and decide what you can do with all those options it is fun. Now you are trapped in the frustrating stage of learning :) But compare it with installing manjaro or ubuntu where wpa_supplicant is running, although you have no wifi, or cups is running although you don't have a printer, and as soon as you install connman it is running already. So a zillion useless things are running, it is complicated to make them stop, some are interdependent so you stop one and something else stops, and the distro just doesn't advocate messing with all of these. Just click on guys and change the colors of your icons.

Different mentality.
so i have to manually export XDG_RUNTIME_DIR =/run/user/1002 to get my dbus running
this is abnormal. Please share the output of 
% ls -la $HOME/.66/conf/svscan@ z/
please also share the content of each file from that directory

Last question: where did you get the error message of "XDG_RUNTIME not found"?
z@ obarunS6 ~ % ls -la $HOME/.66/conf/svscan@ z/
total 12K
drwxr-xr-x 2 z users 4.0K Feb 20 07:31  ./
drwxr-xr-x 5 z users 4.0K Feb 20 07:31  ../
-rw-r--r-- 1 z users  374 Feb 20 22:31 'svscan@ z'

z@ obarunS6 [1] ~ % cat /home/z/.66/conf/svscan@ z/svscan@ z 
HOME=/home/z
LOGNAME=z
USER=z
PATH=/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin
SHELL=/bin/zsh
DISPLAY=:0
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1002/bus
XDG_RUNTIME_DIR=/run/user/1002
XDG_CACHE_HOME=/home/z/.cache
XDG_CONFIG_HOME=/home/z/.config
XDG_DATA_HOME=/home/z/.local/share
XDG_DATA_DIRS=/home/z/.local/share:/usr/local/share:/usr/share
XDG_SESSION_CLASS=user
z@ obarunS6 ~ %
everything normal i guess. but the .xinitrc just not does it.
when i start xfce i notice dbus (eg. pulse) is not working, so i go back to the shell type just "dbus-launch" and there i get the error message (or when i type it a terminal window).
after "export XDG_RUNTIME_DIR =/run/user/1002" before starting x everything seems to work now.
have you tried removing .config/pulse?
@ negative
I think it's not the problem. His svscan@ z should not start correctly.
If i read this thread correctly, he did not enable again the boot-user@ z correctly
66-enable -t boot-user boot-user@ z
it should be 
# 66-enable -t boot-user -F boot-user@ z
the only way to be sure it's that udo post again the output of 66-intree -zg as root and z regular user.
z@ obarunS6 ~ % 66-intree -zg   
Name         : base
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : z
Symlinks     : svc->source db->source
Contents     : /
               ├─(18074,Enabled,longrun) pulseaudio-log
               ├─(18287,Enabled,longrun) pulseaudio
               ├─(18353,Enabled,longrun) dbus-session@ z-log
               └─(18358,Enabled,longrun) dbus-session@ z

z@ obarunS6 ~ % sudo 66-intree -zg 
[sudo] password for z: 
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(175,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,oneshot) system-hwclock
               ├─(up,Enabled,oneshot) modules-kernel
               ├─(up,Enabled,oneshot) system-random
               ├─(up,Enabled,oneshot) modules-system
               ├─(up,Enabled,oneshot) system-sysctl
               ├─(218,Enabled,longrun) udevd-log
               ├─(394,Enabled,longrun) udevd
               ├─(up,Enabled,oneshot) udevadm
               ├─(up,Enabled,oneshot) system-fontnkey
               ├─(up,Enabled,bundle) all-Mount
               ├─(up,Enabled,oneshot) system-fsck
               ├─(up,Enabled,oneshot) mount-fstab
               ├─(up,Enabled,bundle) all-System
               ├─(up,Enabled,oneshot) mount-rw
               ├─(up,Enabled,oneshot) local-loop
               ├─(up,Enabled,oneshot) local-sethostname
               ├─(up,Enabled,oneshot) local-time
               ├─(up,Enabled,oneshot) local-tmpfiles
               ├─(up,Enabled,oneshot) local-authfiles
               ├─(up,Enabled,oneshot) local-dmesg
               ├─(up,Enabled,oneshot) mount-netfs
               ├─(up,Enabled,bundle) all-Local
               ├─(up,Enabled,oneshot) all-Runtime
               ├─(up,Enabled,bundle) All
               ├─(820,Enabled,longrun) tty-rc@ tty2
               ├─(819,Enabled,longrun) tty-rc@ tty1
               └─(up,Enabled,module) boot@ system

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(675,Enabled,classic) wpa_supplicant-log
               ├─(0,Enabled,classic) wpa_supplicant
               ├─(682,Enabled,classic) dhcpcd-log
               ├─(681,Enabled,classic) dhcpcd
               ├─(684,Enabled,classic) cupsd-log
               ├─(685,Enabled,classic) bluetoothd-log
               ├─(835,Enabled,classic) bluetoothd
               ├─(683,Enabled,classic) cupsd
               ├─(708,Enabled,longrun) dbus-log
               ├─(718,Enabled,longrun) dbus
               ├─(711,Enabled,longrun) connmand-log
               ├─(737,Enabled,longrun) connmand
               ├─(709,Enabled,longrun) consolekit-log
               └─(736,Enabled,longrun) consolekit

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

z@ obarunS6 ~ %
Your system for the root user part seems now correct.
Can please you post the output of 
% 66-inservice -o logfile -p 50 pulseaudio

Powered by Obarun