I think I might have screwed up the 66 init system. I tried following the instructions of the last user, eric, on a sound system thread:
https://forum.obarun.org/viewtopic.php?id=440

However, this is what I get when I run those commands: 
> # Run as regular user
> 66-enable -S pipewire pipewire-media-session pipewire-pulse
66-enable: fatal: unable to find the current tree. You must use -t options
> sudo !!
sudo 66-enable -S pipewire pipewire-media-session pipewire-pulse
[sudo] password for myUser:
66-enable: fatal: unable to parse service file: /usr/lib/66/service/user/pipewire: or its dependencies
> sudo 66-enable -t root pipewire
[sudo] password for myUser:
66-enable: fatal: unable to parse service file: /usr/lib/66/service/user/pipewire: or its dependencies
Pretty sure that this is happening when I broke the 66 init system by trying to follow the instructions for using sway on Obarun that was detailed in this thread:
https://forum.obarun.org/viewtopic.php?id=1392

As a result, each time I start up my system, I have to login on a tty, and then I have to manually start sway or startx. I don't really care about that too much, as I just want get sound working at the moment.

So a lot of the trees on my system have been kind of weird: 
> sudo 66-intree -z -g
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(288,Enabled,classic) tty-earlier@ tty12
               ├─(down,Enabled,oneshot) system-hostname
               ├─(down,Enabled,oneshot) mount-run
               ├─(down,Enabled,oneshot) populate-run
               ├─(down,Enabled,oneshot) mount-tmp
               ├─(down,Enabled,oneshot) populate-tmp
               ├─(down,Enabled,oneshot) mount-proc
               ├─(down,Enabled,oneshot) mount-sys
               ├─(down,Enabled,oneshot) populate-sys
               ├─(down,Enabled,oneshot) mount-dev
               ├─(down,Enabled,oneshot) mount-pts
               ├─(down,Enabled,oneshot) mount-shm
               ├─(down,Enabled,oneshot) populate-dev
               ├─(down,Enabled,oneshot) mount-cgroups
               ├─(down,Enabled,bundle) 00
               ├─(down,Enabled,oneshot) system-hwclock
               ├─(down,Enabled,oneshot) modules-kernel
               ├─(down,Enabled,oneshot) system-random
               ├─(down,Enabled,oneshot) modules-system
               ├─(down,Enabled,oneshot) system-sysctl
               ├─(334,Enabled,longrun) udevd-log
               ├─(508,Enabled,longrun) udevd
               ├─(down,Enabled,oneshot) udevadm
               ├─(down,Enabled,oneshot) system-fontnkey
               ├─(down,Enabled,bundle) all-Mount
               ├─(down,Enabled,oneshot) system-fsck
               ├─(down,Enabled,oneshot) mount-fstab
               ├─(down,Enabled,bundle) all-System
               ├─(down,Enabled,oneshot) mount-rw
               ├─(down,Enabled,oneshot) mount-netfs
               ├─(down,Enabled,oneshot) local-loop
               ├─(down,Enabled,oneshot) local-sethostname
               ├─(down,Enabled,oneshot) local-time
               ├─(down,Enabled,oneshot) local-authfiles
               ├─(down,Enabled,oneshot) local-tmpfiles
               ├─(down,Enabled,oneshot) local-dmesg
               ├─(down,Enabled,bundle) all-Local
               ├─(down,Enabled,oneshot) all-Runtime
               ├─(down,Enabled,bundle) All
               ├─(0,Enabled,longrun) tty-rc@ tty1
               ├─(0,Enabled,longrun) tty-rc@ tty2
               └─(down,Enabled,module) boot@ system

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(827,Enabled,classic) cupsd-log
               ├─(825,Enabled,classic) wpa_supplicant-nl80211@ wlo1-log
               ├─(826,Enabled,classic) wpa_supplicant-nl80211@ wlo1
               └─(828,Enabled,classic) cupsd

Name         : desktop
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) setenv@ obgreet
               ├─(888,Enabled,longrun) svscan@ obgreet-log
               ├─(951,Enabled,longrun) svscan@ obgreet
               ├─(up,Enabled,module) scandir@ obgreet
               ├─(up,Enabled,oneshot) mount-run@ obgreet
               ├─(891,Enabled,longrun) dbus-log
               ├─(906,Enabled,longrun) dbus
               ├─(890,Enabled,longrun) seatd-log
               ├─(905,Enabled,longrun) seatd
               ├─(889,Enabled,longrun) greetd-log
               ├─(0,Enabled,longrun) greetd
               ├─(up,Enabled,module) display-manager@ greetd
               ├─(up,Enabled,module) console-tracker@ seatd
               ├─(up,Enabled,module) boot-user@ obgreet
               ├─(up,Enabled,oneshot) setenv@ myUser
               ├─(887,Enabled,longrun) svscan@ myUser-log
               ├─(952,Enabled,longrun) svscan@ myUser
               ├─(up,Enabled,module) scandir@ myUser
               ├─(up,Enabled,oneshot) mount-run@ myUser
               └─(up,Enabled,module) boot-user@ myUser

Name         : net
Initialized  : yes
Enabled      : yes
Starts after : root desktop
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(966,Enabled,classic) openntpd-log
               ├─(969,Enabled,classic) openntpd
               ├─(968,Enabled,classic) dhcpcd-log
               ├─(825,Enabled,classic) wpa_supplicant-nl80211@ wlo1-log
               ├─(970,Enabled,classic) dhcpcd
               ├─(826,Enabled,classic) wpa_supplicant-nl80211@ wlo1
               ├─(0,Disabled,classic) wpa_supplicant-log
               └─(0,Disabled,classic) wpa_supplicant

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

Name         : myUser
Initialized  : no
Enabled      : yes
Starts after : root desktop net boot-user
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               └─None
As a result, I've had to login through a tty and then manually execute sway or startx. I don't really care about that too much at the moment since I just want to get sound working.
66-enable: fatal: unable to find the current tree. You must use -t options
This error means that 66 cannot find automatically the tree to use to enable the service. As you can see at the 66-intree output you have a field called current. This field give you the tree currently in used if you don't specify the tree to use at command line by the -t options.
So, here you try to resolve you issue passing through the superuser which is not the problem and will give you more issue to solve :).
The first thing to do is to find out the current tree as regular user. You can find it easily with the command 66-intree -zg launched by the regular user. In your case i guess that you don't have any regular tree created. If i suppose correctly, i advice you to create one with the 66-tree tool than enable the pipewire pipewire-media-session pipewire-pulse inside it (as regular user obviously).
Also, i encourage you to increase your verbosity (-v3) when you get stuck on this kind of difficulties. 66 tools will give you a lot of informations of what it do and why it crash.

No, you seem to have a trouble at your boot tree. Seeing down is not really a good sign. You should look at your uncaught-log (meaning log of the boot) at /run/66/log/0/current file. If you want more informations increase the verbosity at the /etc/66/init.conf file with VERBOSITY=3.
I followed your advice for the audio and set VERBOSITY=3 in /etc/66/init.conf. 
> 66-tree -a myUser -n audio
...
...
[ Didn't bother recording output ]
> 66-enable -t audio pipewire pipewire-media-session pipewire-pulse
...
...
[ Didn't bother recording output ]
> 66-intree -z -g audio
Name         : audio
Initialized  : no
Enabled      : no
Starts after : None
Current      : no
Allowed      : myUser
Symlinks     : svc->source db->source
Contents     : /
               ├─(0,Enabled,longrun) pipewire-media-session-log
               ├─(0,Enabled,longrun) pipewire-log
               ├─(0,Enabled,longrun) pipewire
               ├─(0,Enabled,longrun) pipewire-pulse-log
               ├─(0,Enabled,longrun) pipewire-pulse
               └─(0,Enabled,longrun) pipewire-media-session
> 66-start -t audio pipewire
66-start: info: Initialized successfully: pipewire-pulse-log
66-start: info: Initialized successfully: pipewire-log
66-start: info: Initialized successfully: pipewire
66-start: info: Initialized successfully: pipewire-pulse
66-start: info: Initialized successfully: pipewire-media-session-log
66-start: info: Initialized successfully: pipewire-media-session
66-start: info: Started successfully: pipewire-log
66-start: info: Started successfully: pipewire
> 66-start -t audio pipewire-pulse pipewire-media-session
66-start: info: Already up: pipewire-log
66-start: info: Already up: pipewire
66-start: info: Started successfully: pipewire-pulse-log
66-start: info: Started successfully: pipewire-pulse
66-start: info: Started successfully: pipewire-media-session-log
66-start: info: Started successfully: pipewire-media-session
> 66-intree -z -g audio
Name         : audio
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : myUser
Symlinks     : svc->source db->source
Contents     : /
               ├─(2745,Enabled,longrun) pipewire-media-session-log
               ├─(2639,Enabled,longrun) pipewire-log
               ├─(2643,Enabled,longrun) pipewire
               ├─(2744,Enabled,longrun) pipewire-pulse-log
               ├─(2752,Enabled,longrun) pipewire-pulse
               └─(2753,Enabled,longrun) pipewire-media-session
> pactl info
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
The audio doesn't appear to work even after manually starting the pipewire service. I might be missing some steps, but I checked the Arch wiki
https://wiki.archlinux.org/title/PipeWire# PulseAudio_clients, and it seems that audio should be working after the service is enabled.

As for the contents of /run/66/log/0/current, all I see is "s6-log: fatal: unable to lock /var/log/66/svscan@ myUser/lock: Device or resource busy"
repeating.
Seems you dont have your audio tree enabled. I also was having problems with audio, and had to enable the same services you use in my user tree before login, or my sound card isn't detected.

You gotta:

66-tree -E audio

then relogin or reboot if relogin doesnt work.
Doesn't seem to have changed that much. 
> 66-intree -z -g audio
Name         : audio
Initialized  : no
Enabled      : yes
Starts after : None
Current      : no
Allowed      : myUser
Symlinks     : svc->source db->source
Contents     : /
               ├─(0,Enabled,longrun) pipewire-media-session-log
               ├─(0,Enabled,longrun) pipewire-log
               ├─(0,Enabled,longrun) pipewire
               ├─(0,Enabled,longrun) pipewire-pulse-log
               ├─(0,Enabled,longrun) pipewire-pulse
               └─(0,Enabled,longrun) pipewire-media-session
> pactl info # Obviously won't work since no pipewire services are running
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
> 66-start -t audio pipewire pipewire-media-session pipewire-pulse
66-start: info: Initialized successfully: pipewire-pulse-log
66-start: info: Initialized successfully: pipewire-log
66-start: info: Initialized successfully: pipewire
66-start: info: Initialized successfully: pipewire-pulse
66-start: info: Initialized successfully: pipewire-media-session-log
66-start: info: Initialized successfully: pipewire-media-session
66-start: info: Started successfully: pipewire-log
66-start: info: Started successfully: pipewire
66-start: info: Started successfully: pipewire-media-session-log
66-start: info: Started successfully: pipewire-media-session
66-start: info: Started successfully: pipewire-pulse-log
66-start: info: Started successfully: pipewire-pulse
> pactl info                                                      
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
Puzzling that the tree isnt getting initialized at login. You shouldn't need to use 66-start once you enable the tree.

Edit: You may have to run %66-update -d (dry run first) to see if you can then run %66-update, and see if that clears whatever is blocking the tree from initializing all services in it automatically at login.
I'm so confuse now with 66 eco system
please post again the output of 66-intree -g as root and regular user
> 66-update -d
66-update: info: dry run do: save state of tree: audio
66-update: info: dry run do: save service(s) list of tree: audio
66-update: info: dry run do: update /run/66/tree/1000/audio to: /tmp/audio:ZMvhVB/audio
66-update: info: dry run do: 66-tree -l /run/66/ -R audio
66-update: info: dry run do: 66-tree -l /run/66/ -nE -a myUser audio
66-update: info: dry run do: 66-tree -S audio audio
66-update: info: dry run do: enable service(s) of tree: audio
66-update: info: dry run do: update db: /run/66/tree/1000/audio to: /home/myUser/.66/system/audio/servicedirs/db/audio
66-update: info: dry run do: tree: audio updated successfully
> 66-update
66-update: info: save state of tree: audio
66-update: info: save service(s) list of tree: audio
66-update: info: update /run/66/tree/1000/audio to: /tmp/audio:eYeSVM/audio
66-tree: info: Disabled successfully tree: audio
66-tree: info: Deleted successfully: audio
66-tree: info: Created successfully tree: audio
66-tree: info: Enabled successfully tree: audio
66-tree: info: Ordered successfully: audio starts after tree: audio
66-update: info: enable service(s) of tree: audio
66-update: info: update db: /run/66/tree/1000/audio to: /home/myUser/.66/system/audio/servicedirs/db/audio
66-tree -R boot-user # didn't actually run this
Is this a trick? I'm having a hard time trying to tell... According to the man pages, the -R flag deletes a tree, completely removing the given tree from the system.
please post again the output of 66-intree -g as root and regular user 
> 66-intree -z -g
Name         : audio
Initialized  : no
Enabled      : yes
Starts after : None
Current      : no
Allowed      : myUser
Symlinks     : svc->source db->source
Contents     : /
               ├─(0,Enabled,longrun) pipewire-media-session-log
               ├─(0,Enabled,longrun) pipewire-log
               ├─(0,Enabled,longrun) pipewire
               ├─(0,Enabled,longrun) pipewire-pulse-log
               ├─(0,Enabled,longrun) pipewire-pulse
               └─(0,Enabled,longrun) pipewire-media-session
> sudo 66-intree -z -g
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(280,Enabled,classic) tty-earlier@ tty12
               ├─(down,Enabled,oneshot) system-hostname
               ├─(down,Enabled,oneshot) mount-run
               ├─(down,Enabled,oneshot) populate-run
               ├─(down,Enabled,oneshot) mount-tmp
               ├─(down,Enabled,oneshot) populate-tmp
               ├─(down,Enabled,oneshot) mount-proc
               ├─(down,Enabled,oneshot) mount-sys
               ├─(down,Enabled,oneshot) populate-sys
               ├─(down,Enabled,oneshot) mount-dev
               ├─(down,Enabled,oneshot) mount-pts
               ├─(down,Enabled,oneshot) mount-shm
               ├─(down,Enabled,oneshot) populate-dev
               ├─(down,Enabled,oneshot) mount-cgroups
               ├─(down,Enabled,bundle) 00
               ├─(down,Enabled,oneshot) system-hwclock
               ├─(down,Enabled,oneshot) modules-kernel
               ├─(down,Enabled,oneshot) system-random
               ├─(down,Enabled,oneshot) modules-system
               ├─(down,Enabled,oneshot) system-sysctl
               ├─(328,Enabled,longrun) udevd-log
               ├─(501,Enabled,longrun) udevd
               ├─(down,Enabled,oneshot) udevadm
               ├─(down,Enabled,oneshot) system-fontnkey
               ├─(down,Enabled,bundle) all-Mount
               ├─(down,Enabled,oneshot) system-fsck
               ├─(down,Enabled,oneshot) mount-fstab
               ├─(down,Enabled,bundle) all-System
               ├─(down,Enabled,oneshot) mount-rw
               ├─(down,Enabled,oneshot) mount-netfs
               ├─(down,Enabled,oneshot) local-loop
               ├─(down,Enabled,oneshot) local-sethostname
               ├─(down,Enabled,oneshot) local-time
               ├─(down,Enabled,oneshot) local-authfiles
               ├─(down,Enabled,oneshot) local-tmpfiles
               ├─(down,Enabled,oneshot) local-dmesg
               ├─(down,Enabled,bundle) all-Local
               ├─(down,Enabled,oneshot) all-Runtime
               ├─(down,Enabled,bundle) All
               ├─(0,Enabled,longrun) tty-rc@ tty1
               ├─(0,Enabled,longrun) tty-rc@ tty2
               └─(down,Enabled,module) boot@ system

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(825,Enabled,classic) cupsd-log
               ├─(824,Enabled,classic) wpa_supplicant-nl80211@ wlo1-log
               ├─(823,Enabled,classic) wpa_supplicant-nl80211@ wlo1
               └─(826,Enabled,classic) cupsd

Name         : desktop
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) setenv@ obgreet
               ├─(888,Enabled,longrun) svscan@ obgreet-log
               ├─(949,Enabled,longrun) svscan@ obgreet
               ├─(up,Enabled,module) scandir@ obgreet
               ├─(up,Enabled,oneshot) mount-run@ obgreet
               ├─(891,Enabled,longrun) dbus-log
               ├─(906,Enabled,longrun) dbus
               ├─(889,Enabled,longrun) seatd-log
               ├─(904,Enabled,longrun) seatd
               ├─(890,Enabled,longrun) greetd-log
               ├─(0,Enabled,longrun) greetd
               ├─(up,Enabled,module) display-manager@ greetd
               ├─(up,Enabled,module) console-tracker@ seatd
               ├─(up,Enabled,module) boot-user@ obgreet
               ├─(up,Enabled,oneshot) setenv@ myUser
               ├─(886,Enabled,longrun) svscan@ myUser-log
               ├─(948,Enabled,longrun) svscan@ myUser
               ├─(up,Enabled,module) scandir@ myUser
               ├─(up,Enabled,oneshot) mount-run@ myUser
               └─(up,Enabled,module) boot-user@ myUser

Name         : net
Initialized  : yes
Enabled      : yes
Starts after : root desktop
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(963,Enabled,classic) openntpd-log
               ├─(964,Enabled,classic) openntpd
               ├─(966,Enabled,classic) dhcpcd-log
               ├─(824,Enabled,classic) wpa_supplicant-nl80211@ wlo1-log
               ├─(965,Enabled,classic) dhcpcd
               ├─(823,Enabled,classic) wpa_supplicant-nl80211@ wlo1
               ├─(0,Disabled,classic) wpa_supplicant-log
               └─(0,Disabled,classic) wpa_supplicant

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

Name         : myUser
Initialized  : no
Enabled      : yes
Starts after : root desktop net boot-user
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               └─None
Think I might have found a hint. 
> PULSE_LOG=4 pactl info -vvv
Parsing configuration file '/etc/pulse/client.conf'
/etc/pulse/client.conf.d does not exist, ignoring.
Using shared memfd memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65472
Trying to connect to /run/users/1000/pulse/native...
connect(): No such file or directory (2)
Trying to connect to /var/run/pulse/native...
connect(): No such file or directory (2)
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
sudo pacman -S pulseaudio-66serv
[sudo] password for myUser: 
resolving dependencies...
looking for conflicting packages...

Packages (1) pulseaudio-66serv-0.2.0-1

Total Download Size:   0.00 MiB
Total Installed Size:  0.00 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 pulseaudio-66ser...     3.3 KiB  2.92 KiB/s 00:01 [# #######################] 100%
(1/1) checking keys in keyring                     [# #######################] 100%
(1/1) checking package integrity                   [# #######################] 100%
(1/1) loading package files                        [# #######################] 100%
(1/1) checking for file conflicts                  [# #######################] 100%
(1/1) checking available disk space                [# #######################] 100%
:: Running pre-transaction hooks...
(1/1) Checking Arch News with Informant ...
There are no unread news items
:: Processing package changes...
(1/1) installing pulseaudio-66serv                 [# #######################] 100%
> pacman -Ql pulseaudio-66serv
pulseaudio-66serv /usr/
pulseaudio-66serv /usr/lib/
pulseaudio-66serv /usr/lib/66/
pulseaudio-66serv /usr/lib/66/service/
pulseaudio-66serv /usr/lib/66/service/pulseaudio
pulseaudio-66serv /usr/share/
pulseaudio-66serv /usr/share/licenses/
pulseaudio-66serv /usr/share/licenses/pulseaudio-66serv/
pulseaudio-66serv /usr/share/licenses/pulseaudio-66serv/LICENSE
> cat /usr/lib/66/service/pulseaudio
[main]
@ type = longrun
@ version = 0.2.0
@ description = "Start a pulseaudio session"
@ user = ( user )
@ options = ( log )

[start]
@ build = auto
@ execute=(
	execl-toc -S ${XDG_RUNTIME_DIR}/pulse/native -m 0755
	pulseaudio --daemonize=no
)

[stop]
@ build = auto
@ execute = ( pulseaudio --kill )

> which pulseaudio
pulseaudio not found
It would appear that the line 'execl-toc -S ${XDG_RUNTIME_DIR}/pulse/native -m 0755' would create the socket file for the function pa_context_connect to call the system call connect on.

Interestingly enough, I don't even have the XDG_RUNTIME variable set. 
> echo $XDG_RUNTIME
Do I need to install the pulseaudio package? Here's what I get if I try 
> pacman -Ss pulseaudio
obextra/pipewire-alsa 1:0.3.48-2
    Low-latency audio/video router and processor - ALSA configuration
obextra/pipewire-pulse 1:0.3.48-2 [installed]
    Low-latency audio/video router and processor - PulseAudio replacement
obextra/pulseaudio 15.0-3
    A featureful, general-purpose sound server
...
The strange thing though is that pipewire-pulse claims to be a PulseAudio replacement.
Pipewire-pulse is a pulsaudio replacement, it conflicts if you try to install them both.

XDG may be your issue, you havent installed xdg-user-dirs-66serv and started it alongside pipewire related services.

However services in your boot&your boot-user tree aren't starting and that could be problematic

Plz Post output of:
%cat /run/66/log/0/current

Edit: Meanwhile you can bypass 66 and temporalily create an .xprofile file in home directory (~/.xprofile).

pipewire &
pipewire-pulse &
pipewire-media-session &

see if that works to connect to your soundcard.
Galeano, I don't know if you read one of my previous posts, but here's what I said:
Is this a trick? I'm having a hard time trying to tell... According to the man pages, the -R flag deletes a tree, completely removing the given tree from the system.
You gave the command '66-tree -R boot-user' without explanation and I was hesitant to execute it because it sounded like the kind of command that would break something. After all, the man page for 66-tree said that it could not be undone.

I don't believe that I whined, but if it sounded like I did, then I apologize. I ended up executing the command and I'll admit that you were right. It's fixed the output of /run/66/log/0/current:
2022-04-19 15:56:58.887018396  [Initiate db of tree boot...]
2022-04-19 15:56:58.888730587  66-init: tracing: initiate db of tree: boot ...
2022-04-19 15:56:58.901154246  66-init: tracing: Write state file of: system-hostname
2022-04-19 15:56:58.901159435  66-init: info: Initialized successfully: system-hostname
2022-04-19 15:56:58.901162000  66-init: tracing: Write state file of: mount-run
2022-04-19 15:56:58.901163563  66-init: info: Initialized successfully: mount-run
2022-04-19 15:56:58.901165086  66-init: tracing: Write state file of: populate-run
2022-04-19 15:56:58.901166569  66-init: info: Initialized successfully: populate-run
2022-04-19 15:56:58.901172830  66-init: tracing: Write state file of: mount-tmp
2022-04-19 15:56:58.901174303  66-init: info: Initialized successfully: mount-tmp
2022-04-19 15:56:58.901175666  66-init: tracing: Write state file of: populate-tmp
2022-04-19 15:56:58.901177088  66-init: info: Initialized successfully: populate-tmp
2022-04-19 15:56:58.901178451  66-init: tracing: Write state file of: mount-proc
2022-04-19 15:56:58.901181066  66-init: info: Initialized successfully: mount-proc
2022-04-19 15:56:58.901182559  66-init: tracing: Write state file of: mount-sys
2022-04-19 15:56:58.901193569  66-init: info: Initialized successfully: mount-sys
2022-04-19 15:56:58.901194892  66-init: tracing: Write state file of: populate-sys
2022-04-19 15:56:58.901196174  66-init: info: Initialized successfully: populate-sys
2022-04-19 15:56:58.901197426  66-init: tracing: Write state file of: mount-dev
2022-04-19 15:56:58.901198679  66-init: info: Initialized successfully: mount-dev
2022-04-19 15:56:58.901199931  66-init: tracing: Write state file of: mount-pts
2022-04-19 15:56:58.901201184  66-init: info: Initialized successfully: mount-pts
2022-04-19 15:56:58.901202426  66-init: tracing: Write state file of: mount-shm
2022-04-19 15:56:58.901203688  66-init: info: Initialized successfully: mount-shm
2022-04-19 15:56:58.901204951  66-init: tracing: Write state file of: populate-dev
2022-04-19 15:56:58.901206223  66-init: info: Initialized successfully: populate-dev
2022-04-19 15:56:58.901207485  66-init: tracing: Write state file of: mount-cgroups
2022-04-19 15:56:58.901208758  66-init: info: Initialized successfully: mount-cgroups
2022-04-19 15:56:58.901209970  66-init: tracing: Write state file of: 00
2022-04-19 15:56:58.901211483  66-init: info: Initialized successfully: 00
2022-04-19 15:56:58.901212755  66-init: tracing: Write state file of: system-hwclock
2022-04-19 15:56:58.901214509  66-init: info: Initialized successfully: system-hwclock
2022-04-19 15:56:58.901215781  66-init: tracing: Write state file of: modules-kernel
2022-04-19 15:56:58.901217304  66-init: info: Initialized successfully: modules-kernel
2022-04-19 15:56:58.901218566  66-init: tracing: Write state file of: system-random
2022-04-19 15:56:58.901225128  66-init: info: Initialized successfully: system-random
2022-04-19 15:56:58.901226471  66-init: tracing: Write state file of: modules-system
2022-04-19 15:56:58.901227753  66-init: info: Initialized successfully: modules-system
2022-04-19 15:56:58.901229016  66-init: tracing: Write state file of: system-sysctl
2022-04-19 15:56:58.901230288  66-init: info: Initialized successfully: system-sysctl
2022-04-19 15:56:58.901231520  66-init: tracing: Write state file of: udevd-log
2022-04-19 15:56:58.901232763  66-init: info: Initialized successfully: udevd-log
2022-04-19 15:56:58.901233985  66-init: tracing: Write state file of: udevd
2022-04-19 15:56:58.901235207  66-init: info: Initialized successfully: udevd
2022-04-19 15:56:58.901236430  66-init: tracing: Write state file of: udevadm
2022-04-19 15:56:58.901237672  66-init: info: Initialized successfully: udevadm
2022-04-19 15:56:58.901238934  66-init: tracing: Write state file of: system-fontnkey
2022-04-19 15:56:58.901240207  66-init: info: Initialized successfully: system-fontnkey
2022-04-19 15:56:58.901241439  66-init: tracing: Write state file of: all-Mount
2022-04-19 15:56:58.901242691  66-init: info: Initialized successfully: all-Mount
2022-04-19 15:56:58.901243934  66-init: tracing: Write state file of: system-fsck
2022-04-19 15:56:58.901253091  66-init: info: Initialized successfully: system-fsck
2022-04-19 15:56:58.901254383  66-init: tracing: Write state file of: mount-fstab
2022-04-19 15:56:58.901255656  66-init: info: Initialized successfully: mount-fstab
2022-04-19 15:56:58.901256888  66-init: tracing: Write state file of: all-System
2022-04-19 15:56:58.901258140  66-init: info: Initialized successfully: all-System
2022-04-19 15:56:58.901259373  66-init: tracing: Write state file of: mount-rw
2022-04-19 15:56:58.901260615  66-init: info: Initialized successfully: mount-rw
2022-04-19 15:56:58.901261857  66-init: tracing: Write state file of: mount-netfs
2022-04-19 15:56:58.901263120  66-init: info: Initialized successfully: mount-netfs
2022-04-19 15:56:58.901264362  66-init: tracing: Write state file of: local-loop
2022-04-19 15:56:58.901265604  66-init: info: Initialized successfully: local-loop
2022-04-19 15:56:58.901266887  66-init: tracing: Write state file of: local-sethostname
2022-04-19 15:56:58.901268169  66-init: info: Initialized successfully: local-sethostname
2022-04-19 15:56:58.901276204  66-init: tracing: Write state file of: local-time
2022-04-19 15:56:58.901277507  66-init: info: Initialized successfully: local-time
2022-04-19 15:56:58.901278779  66-init: tracing: Write state file of: local-authfiles
2022-04-19 15:56:58.901280051  66-init: info: Initialized successfully: local-authfiles
2022-04-19 15:56:58.901281324  66-init: tracing: Write state file of: local-tmpfiles
2022-04-19 15:56:58.901282596  66-init: info: Initialized successfully: local-tmpfiles
2022-04-19 15:56:58.901283849  66-init: tracing: Write state file of: local-dmesg
2022-04-19 15:56:58.901285111  66-init: info: Initialized successfully: local-dmesg
2022-04-19 15:56:58.901286353  66-init: tracing: Write state file of: all-Local
2022-04-19 15:56:58.901287596  66-init: info: Initialized successfully: all-Local
2022-04-19 15:56:58.901288848  66-init: tracing: Write state file of: all-Runtime
2022-04-19 15:56:58.901294448  66-init: info: Initialized successfully: all-Runtime
2022-04-19 15:56:58.901295681  66-init: tracing: Write state file of: All
2022-04-19 15:56:58.901296913  66-init: info: Initialized successfully: All
2022-04-19 15:56:58.901298165  66-init: tracing: Write state file of: tty-rc@ tty1
2022-04-19 15:56:58.901299438  66-init: info: Initialized successfully: tty-rc@ tty1
2022-04-19 15:56:58.901300690  66-init: tracing: Write state file of: tty-rc@ tty2
2022-04-19 15:56:58.901301963  66-init: info: Initialized successfully: tty-rc@ tty2
2022-04-19 15:56:58.901303215  66-init: tracing: Write state file of: boot@ system
2022-04-19 15:56:58.901304487  66-init: info: Initialized successfully: boot@ system
2022-04-19 15:56:58.901797472  [Start db services of tree boot...]
2022-04-19 15:56:58.905753230  s6-rc: info: bringing selected services up
2022-04-19 15:56:58.906052511  s6-rc: info: service s6rc-fdholder: starting
2022-04-19 15:56:58.906301358  s6-rc: info: service s6rc-oneshot-runner: starting
2022-04-19 15:56:58.909532417  s6-rc: info: service s6rc-oneshot-runner successfully started
2022-04-19 15:56:58.909793878  s6-rc: info: service system-hostname: starting
2022-04-19 15:56:58.909869530  s6-rc: info: service mount-tmp: starting
2022-04-19 15:56:58.909944971  s6-rc: info: service mount-run: starting
2022-04-19 15:56:58.909999604  s6-rc: info: service mount-proc: starting
2022-04-19 15:56:58.912151128  s6-rc: info: service s6rc-fdholder successfully started
2022-04-19 15:56:58.912213786  s6-rc: info: service udevd-log: starting
2022-04-19 15:56:58.913596388  system-hostname: info: starts...
2022-04-19 15:56:58.913600206  mount-tmp: info: starts...
2022-04-19 15:56:58.913607078  mount-proc: info: starts...
2022-04-19 15:56:58.913640451  mount-run: info: starts...
2022-04-19 15:56:58.914904502  s6-rc: info: service mount-run successfully started
2022-04-19 15:56:58.914981195  s6-rc: info: service populate-run: starting
2022-04-19 15:56:58.914997957  s6-rc: info: service mount-proc successfully started
2022-04-19 15:56:58.915066415  s6-rc: info: service mount-sys: starting
2022-04-19 15:56:58.915291768  s6-rc: info: service udevd-log successfully started
2022-04-19 15:56:58.916614839  populate-run: info: starts...
2022-04-19 15:56:58.917564159  s6-rc: info: service system-hostname successfully started
2022-04-19 15:56:58.917776317  mount-sys: info: starts...
2022-04-19 15:56:58.918669793  s6-rc: info: service mount-sys successfully started
2022-04-19 15:56:58.918725287  s6-rc: info: service populate-sys: starting
2022-04-19 15:56:58.918788866  s6-rc: info: service mount-dev: starting
2022-04-19 15:56:58.919183496  s6-rc: info: service mount-tmp successfully started
2022-04-19 15:56:58.919240593  s6-rc: info: service populate-tmp: starting
2022-04-19 15:56:58.920454830  populate-sys: info: starts...
2022-04-19 15:56:58.920860641  s6-rc: info: service populate-run successfully started
2022-04-19 15:56:58.921009961  mount-dev: info: starts...
2022-04-19 15:56:58.921204186  populate-tmp: info: starts...
2022-04-19 15:56:58.921772281  s6-rc: info: service mount-dev successfully started
2022-04-19 15:56:58.921826172  s6-rc: info: service populate-dev: starting
2022-04-19 15:56:58.921884982  s6-rc: info: service mount-shm: starting
2022-04-19 15:56:58.921995700  s6-rc: info: service mount-pts: starting
2022-04-19 15:56:58.922047006  s6-rc: info: service mount-cgroups: starting
2022-04-19 15:56:58.922064910  s6-rc: info: service populate-tmp successfully started
2022-04-19 15:56:58.923576474  populate-dev: info: starts...
2022-04-19 15:56:58.923798761  mount-cgroups: info: starts...
2022-04-19 15:56:58.924276878  mount-pts: info: starts...
2022-04-19 15:56:58.924284522  mount-shm: info: starts...
2022-04-19 15:56:58.925628172  s6-rc: info: service mount-shm successfully started
2022-04-19 15:56:58.925633031  s6-rc: info: service mount-pts successfully started
2022-04-19 15:56:58.927018199  s6-rc: info: service populate-dev successfully started
2022-04-19 15:56:58.929901245  s6-rc: info: service populate-sys successfully started
2022-04-19 15:56:59.037284022  s6-rc: info: service mount-cgroups successfully started
2022-04-19 15:56:59.037405029  s6-rc: info: service system-sysctl: starting
2022-04-19 15:56:59.037502512  s6-rc: info: service system-random: starting
2022-04-19 15:56:59.037588503  s6-rc: info: service system-hwclock: starting
2022-04-19 15:56:59.037713637  s6-rc: info: service modules-system: starting
2022-04-19 15:56:59.037807864  s6-rc: info: service modules-kernel: starting
2022-04-19 15:56:59.039302347  system-random: info: starts...
2022-04-19 15:56:59.039308699  system-sysctl: info: starts...
2022-04-19 15:56:59.040162129  modules-kernel: info: starts...
2022-04-19 15:56:59.040276424  system-hwclock: info: starts...
2022-04-19 15:56:59.041419788  modules-system: info: starts...
2022-04-19 15:56:59.041664978  * Applying /etc/sysctl.conf ...
2022-04-19 15:56:59.041666340  kernel.sysrq = 1
2022-04-19 15:56:59.041667062  kernel.core_uses_pid = 1
2022-04-19 15:56:59.041667683  fs.protected_hardlinks = 1
2022-04-19 15:56:59.041668314  fs.protected_symlinks = 1
2022-04-19 15:56:59.041668985  fs.inotify.max_user_instances = 1024
2022-04-19 15:56:59.041669676  fs.inotify.max_user_watches = 524288
2022-04-19 15:56:59.042004795  s6-rc: info: service system-sysctl successfully started
2022-04-19 15:56:59.042538586  s6-rc: info: service system-random successfully started
2022-04-19 15:56:59.048216333  /usr/bin/modules.sh: No modules found -- nothing to do
2022-04-19 15:56:59.049062751  s6-rc: info: service modules-system successfully started
2022-04-19 15:56:59.049408820  s6-rc: info: service system-hwclock successfully started
2022-04-19 15:56:59.121477732  s6-rc: info: service modules-kernel successfully started
2022-04-19 15:56:59.121634886  s6-rc: info: service udevd: starting
2022-04-19 15:57:00.141998580  s6-rc: info: service udevd successfully started
2022-04-19 15:57:00.142129285  s6-rc: info: service udevadm: starting
2022-04-19 15:57:00.144516883  udevadm: info: starts...
2022-04-19 15:57:02.491054059  s6-rc: info: service udevadm successfully started
2022-04-19 15:57:02.491250578  s6-rc: info: service system-fontnkey: starting
2022-04-19 15:57:02.505412776  system-fontnkey: info: starts...
2022-04-19 15:57:02.519588761  s6-rc: info: service system-fontnkey successfully started
2022-04-19 15:57:02.519680342  s6-rc: info: service system-fsck: starting
2022-04-19 15:57:02.527705843  system-fsck: info: starts...
2022-04-19 15:57:02.538768729  system-fsck: info: ROOT: clean, 266580/2949120 files, 4530401/11796480 blocks
2022-04-19 15:57:02.547505784  system-fsck: info: fsck.fat 4.2 (2021-01-31)
2022-04-19 15:57:02.547520111  system-fsck: info: /dev/nvme0n1p1: 8 files, 12272/140520 clusters
2022-04-19 15:57:02.551991616  system-fsck: info: HOME: clean, 219659/11411456 files, 2916298/45621649 blocks
2022-04-19 15:57:02.554684486  s6-rc: info: service system-fsck successfully started
2022-04-19 15:57:02.554760900  s6-rc: info: service mount-fstab: starting
2022-04-19 15:57:02.556346703  mount-fstab: info: starts...
2022-04-19 15:57:02.569713621  s6-rc: info: service mount-fstab successfully started
2022-04-19 15:57:02.569806475  s6-rc: info: service mount-rw: starting
2022-04-19 15:57:02.572435465  mount-rw: info: starts...
2022-04-19 15:57:02.574753562  s6-rc: info: service mount-rw successfully started
2022-04-19 15:57:02.574900367  s6-rc: info: service mount-netfs: starting
2022-04-19 15:57:02.575062862  s6-rc: info: service local-tmpfiles: starting
2022-04-19 15:57:02.575243170  s6-rc: info: service local-time: starting
2022-04-19 15:57:02.575400846  s6-rc: info: service local-sethostname: starting
2022-04-19 15:57:02.575532222  s6-rc: info: service local-loop: starting
2022-04-19 15:57:02.575601552  s6-rc: info: service local-authfiles: starting
2022-04-19 15:57:02.577081287  mount-netfs: info: starts...
2022-04-19 15:57:02.577987647  local-loop: info: starts...
2022-04-19 15:57:02.578245591  local-authfiles: info: starts...
2022-04-19 15:57:02.578284564  local-sethostname: info: starts...
2022-04-19 15:57:02.578291367  s6-rc: info: service mount-netfs successfully started
2022-04-19 15:57:02.578473578  local-time: info: starts...
2022-04-19 15:57:02.578495159  local-tmpfiles: info: starts...
2022-04-19 15:57:02.579560226  s6-rc: info: service local-authfiles successfully started
2022-04-19 15:57:02.581597276  s6-rc: info: service local-loop successfully started
2022-04-19 15:57:02.582587323  s6-rc: info: service local-time successfully started
2022-04-19 15:57:02.582666051  s6-rc: info: service local-sethostname successfully started
2022-04-19 15:57:02.585537485  _d /run/named 0750 named named 0 
2022-04-19 15:57:02.589818123  _d /var/lib/colord 0755 colord colord 0 
2022-04-19 15:57:02.591384420  _d /var/lib/colord/icc 0755 colord colord 0 
2022-04-19 15:57:02.593075722  _d /run/dbus 0755 0 0 0 
2022-04-19 15:57:02.594952482  _d /run/dhcpcd 0755 root root 0 
2022-04-19 15:57:02.596678028  _d /run/fetchmail 700 fetchmail nobody 0 
2022-04-19 15:57:02.598752067  _d /var/lib/fetchmail 755 fetchmail nobody 0 
2022-04-19 15:57:02.601013799  _w /sys/devices/system/cpu/microcode/reload - 0 0 0 1
2022-04-19 15:57:02.602957413  _d /var/cache/man 0755 root root 1w 
2022-04-19 15:57:02.605909109  _d /run/initramfs 0755 root root 0 
2022-04-19 15:57:02.607804152  _d /run/nscd 0755 root root 0 
2022-04-19 15:57:02.610087464  _C /etc/crypttab  0 0 0 
2022-04-19 15:57:02.610485711  _C /etc/fstab  0 0 0 
2022-04-19 15:57:02.610488937  _C /etc/group  0 0 0 
2022-04-19 15:57:02.610490310  _C /etc/gshadow  0 0 0 
2022-04-19 15:57:02.610491512  _C /etc/host.conf  0 0 0 
2022-04-19 15:57:02.610492634  _C /etc/hosts  0 0 0 
2022-04-19 15:57:02.610501902  _C /etc/issue  0 0 0 
2022-04-19 15:57:02.610597551  _C /etc/ld.so.conf  0 0 0 
2022-04-19 15:57:02.610669666  _C /etc/nsswitch.conf  0 0 0 
2022-04-19 15:57:02.610738956  _C /etc/passwd  0 0 0 
2022-04-19 15:57:02.610807595  _C /etc/profile  0 0 0 
2022-04-19 15:57:02.610879470  _C /etc/securetty  0 0 0 
2022-04-19 15:57:02.610950112  _C /etc/shadow  0 0 0 
2022-04-19 15:57:02.610998373  _C /etc/shells  0 0 0 
2022-04-19 15:57:02.611196975  _d /run/faillock 0755 root root 0 
2022-04-19 15:57:02.614168698  _d /var/empty 0755 root root 0 
2022-04-19 15:57:02.615643063  _d /run/sudo 0711 root root 0 
2022-04-19 15:57:02.617452917  _D /run/sudo/ts 0700 root root 0 
2022-04-19 15:57:02.619560068  _d /var/lib/tpm2-tss/system/keystore 2775 tss tss 0 
2022-04-19 15:57:02.621227856  tmpfiles: ignoring invalid entry on line 3 of `/usr/lib/tmpfiles.d/tpm2-tss-fapi.conf'
2022-04-19 15:57:02.621269915  _d /run/tpm2-tss/eventlog 2775 tss tss 0 
2022-04-19 15:57:02.622891596  tmpfiles: ignoring invalid entry on line 5 of `/usr/lib/tmpfiles.d/tpm2-tss-fapi.conf'
2022-04-19 15:57:02.623355396  s6-rc: info: service local-tmpfiles successfully started
2022-04-19 15:57:02.623499256  s6-rc: info: service local-dmesg: starting
2022-04-19 15:57:02.625713037  local-dmesg: info: starts...
2022-04-19 15:57:02.630690622  s6-rc: info: service local-dmesg successfully started
2022-04-19 15:57:02.630845723  s6-rc: info: service all-Runtime: starting
2022-04-19 15:57:02.633920579  all-Runtime: info: starts...
2022-04-19 15:57:02.637959724  66-all: tracing: point symlink: /run/66/state/0/root/servicedirs to /var/lib/66/system/root/servicedirs
2022-04-19 15:57:02.637979641  66-all: tracing: init service: cupsd-log
2022-04-19 15:57:02.637982897  66-all: tracing: copy: /var/lib/66/system/root/servicedirs/svc/cupsd to /run/66/scandir/0/cupsd
2022-04-19 15:57:02.639453465  66-all: tracing: create file: /run/66/scandir/0/cupsd/log/down
2022-04-19 15:57:02.639455459  66-all: tracing: create fifo: /run/66/scandir/0/cupsd/log/event
2022-04-19 15:57:02.639456400  66-all: tracing: subcribe to fifo: /run/66/scandir/0/cupsd/log/event
2022-04-19 15:57:02.639541550  66-all: tracing: init service: cupsd
2022-04-19 15:57:02.639543494  66-all: tracing: create file: /run/66/scandir/0/cupsd/down
2022-04-19 15:57:02.639548753  66-all: tracing: create fifo: /run/66/scandir/0/cupsd/event
2022-04-19 15:57:02.639552340  66-all: tracing: subcribe to fifo: /run/66/scandir/0/cupsd/event
2022-04-19 15:57:02.639626329  66-all: tracing: init service: wpa_supplicant-nl80211@ wlo1-log
2022-04-19 15:57:02.639628764  66-all: tracing: copy: /var/lib/66/system/root/servicedirs/svc/wpa_supplicant-nl80211@ wlo1 to /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1
2022-04-19 15:57:02.640039885  66-all: tracing: create file: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/log/down
2022-04-19 15:57:02.640041498  66-all: tracing: create fifo: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/log/event
2022-04-19 15:57:02.640045916  66-all: tracing: subcribe to fifo: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/log/event
2022-04-19 15:57:02.640334437  66-all: tracing: init service: wpa_supplicant-nl80211@ wlo1
2022-04-19 15:57:02.640336441  66-all: tracing: create file: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/down
2022-04-19 15:57:02.640341951  66-all: tracing: create fifo: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/event
2022-04-19 15:57:02.640345738  66-all: tracing: subcribe to fifo: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/event
2022-04-19 15:57:02.640408816  66-all: tracing: reload scandir: /run/66/scandir/0
2022-04-19 15:57:02.640414898  66-all: tracing: waiting for events on fifo
2022-04-19 15:57:02.641331356  66-all: tracing: delete down file at: /run/66/scandir/0/cupsd/log/down
2022-04-19 15:57:02.641337508  66-all: tracing: delete down file at: /run/66/scandir/0/cupsd/down
2022-04-19 15:57:02.641339983  66-all: tracing: delete down file at: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/log/down
2022-04-19 15:57:02.641341966  66-all: tracing: delete down file at: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/down
2022-04-19 15:57:02.641343650  66-all: tracing: Write state file of: cupsd-log
2022-04-19 15:57:02.641355953  66-all: info: Initialized successfully: cupsd-log
2022-04-19 15:57:02.641357035  66-all: tracing: Write state file of: cupsd
2022-04-19 15:57:02.641373025  66-all: info: Initialized successfully: cupsd
2022-04-19 15:57:02.641373676  66-all: tracing: Write state file of: wpa_supplicant-nl80211@ wlo1-log
2022-04-19 15:57:02.641378996  66-all: info: Initialized successfully: wpa_supplicant-nl80211@ wlo1-log
2022-04-19 15:57:02.641379597  66-all: tracing: Write state file of: wpa_supplicant-nl80211@ wlo1
2022-04-19 15:57:02.641397330  66-all: info: Initialized successfully: wpa_supplicant-nl80211@ wlo1
2022-04-19 15:57:02.642109155  66-all: info: Initialization: no atomic services into tree: root
2022-04-19 15:57:02.642110828  66-all: tracing: reload scandir: /run/66/scandir/0
2022-04-19 15:57:02.642268404  66-all: tracing: sanitize classic services list...
2022-04-19 15:57:02.642269967  66-all: tracing: start classic services list ...
2022-04-19 15:57:02.642627066  66-all: tracing: clean up fifo: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/log/event
2022-04-19 15:57:02.642634230  66-all: tracing: subcribe to fifo: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/log/event
2022-04-19 15:57:02.642709120  66-all: tracing: clean up fifo: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/event
2022-04-19 15:57:02.642715382  66-all: tracing: subcribe to fifo: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/event
2022-04-19 15:57:02.642775465  66-all: tracing: clean up fifo: /run/66/scandir/0/cupsd/log/event
2022-04-19 15:57:02.642781586  66-all: tracing: subcribe to fifo: /run/66/scandir/0/cupsd/log/event
2022-04-19 15:57:02.642840867  66-all: tracing: clean up fifo: /run/66/scandir/0/cupsd/event
2022-04-19 15:57:02.642847119  66-all: tracing: subcribe to fifo: /run/66/scandir/0/cupsd/event
2022-04-19 15:57:02.643006588  66-all: tracing: send signal: uwU to: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/log/supervise
2022-04-19 15:57:02.643049479  66-all: tracing: send signal: u to: /run/66/scandir/0/wpa_supplicant-nl80211@ wlo1/supervise
2022-04-19 15:57:02.643051302  66-all: tracing: send signal: uwU to: /run/66/scandir/0/cupsd/log/supervise
2022-04-19 15:57:02.643093401  66-all: tracing: send signal: u to: /run/66/scandir/0/cupsd/supervise
2022-04-19 15:57:02.646240623  66-all: info: wpa_supplicant-nl80211@ wlo1-log: started successfully
2022-04-19 15:57:02.646243649  66-all: tracing: Write state file of: wpa_supplicant-nl80211@ wlo1-log
2022-04-19 15:57:02.646250492  66-all: info: wpa_supplicant-nl80211@ wlo1: started successfully
2022-04-19 15:57:02.646251363  66-all: tracing: Write state file of: wpa_supplicant-nl80211@ wlo1
2022-04-19 15:57:02.646262484  66-all: info: cupsd-log: started successfully
2022-04-19 15:57:02.646263406  66-all: tracing: Write state file of: cupsd-log
2022-04-19 15:57:02.646272813  66-all: info: cupsd: started successfully
2022-04-19 15:57:02.646273635  66-all: tracing: Write state file of: cupsd
2022-04-19 15:57:02.646419318  66-all: tracing: switch classic service list of: root to source
2022-04-19 15:57:02.647463627  66-all: info: Initialization report: no classic services into tree: desktop
2022-04-19 15:57:02.648280639  66-all: tracing: point symlink: /run/66/state/0/desktop/servicedirs to /var/lib/66/system/desktop/servicedirs
2022-04-19 15:57:02.648285638  66-all: tracing: initiate db of tree: desktop ...
2022-04-19 15:57:02.667874804  66-all: tracing: Write state file of: greetd-log
2022-04-19 15:57:02.667878561  66-all: info: Initialized successfully: greetd-log
2022-04-19 15:57:02.667879573  66-all: tracing: Write state file of: seatd-log
2022-04-19 15:57:02.667886275  66-all: info: Initialized successfully: seatd-log
2022-04-19 15:57:02.667887057  66-all: tracing: Write state file of: seatd
2022-04-19 15:57:02.667887848  66-all: info: Initialized successfully: seatd
2022-04-19 15:57:02.667888540  66-all: tracing: Write state file of: greetd
2022-04-19 15:57:02.667889271  66-all: info: Initialized successfully: greetd
2022-04-19 15:57:02.667890063  66-all: tracing: Write state file of: setenv@ myUser
2022-04-19 15:57:02.667893649  66-all: info: Initialized successfully: setenv@ myUser
2022-04-19 15:57:02.667894461  66-all: tracing: Write state file of: svscan@ myUser-log
2022-04-19 15:57:02.667897797  66-all: info: Initialized successfully: svscan@ myUser-log
2022-04-19 15:57:02.667898609  66-all: tracing: Write state file of: svscan@ myUser
2022-04-19 15:57:02.667903688  66-all: info: Initialized successfully: svscan@ myUser
2022-04-19 15:57:02.667904449  66-all: tracing: Write state file of: scandir@ myUser
2022-04-19 15:57:02.667919337  66-all: info: Initialized successfully: scandir@ myUser
2022-04-19 15:57:02.667920269  66-all: tracing: Write state file of: mount-run@ myUser
2022-04-19 15:57:02.667930498  66-all: info: Initialized successfully: mount-run@ myUser
2022-04-19 15:57:02.667931470  66-all: tracing: Write state file of: boot-user@ myUser
2022-04-19 15:57:02.667935097  66-all: info: Initialized successfully: boot-user@ myUser
2022-04-19 15:57:02.667935888  66-all: tracing: Write state file of: dbus-log
2022-04-19 15:57:02.667939335  66-all: info: Initialized successfully: dbus-log
2022-04-19 15:57:02.667940076  66-all: tracing: Write state file of: dbus
2022-04-19 15:57:02.667943443  66-all: info: Initialized successfully: dbus
2022-04-19 15:57:02.667944284  66-all: tracing: Write state file of: console-tracker@ seatd
2022-04-19 15:57:02.667947640  66-all: info: Initialized successfully: console-tracker@ seatd
2022-04-19 15:57:02.667950907  66-all: tracing: Write state file of: display-manager@ greetd
2022-04-19 15:57:02.667954253  66-all: info: Initialized successfully: display-manager@ greetd
2022-04-19 15:57:02.667955064  66-all: tracing: Write state file of: setenv@ obgreet
2022-04-19 15:57:02.667965434  66-all: info: Initialized successfully: setenv@ obgreet
2022-04-19 15:57:02.667966396  66-all: tracing: Write state file of: svscan@ obgreet-log
2022-04-19 15:57:02.667969742  66-all: info: Initialized successfully: svscan@ obgreet-log
2022-04-19 15:57:02.667970543  66-all: tracing: Write state file of: svscan@ obgreet
2022-04-19 15:57:02.667973900  66-all: info: Initialized successfully: svscan@ obgreet
2022-04-19 15:57:02.667974741  66-all: tracing: Write state file of: scandir@ obgreet
2022-04-19 15:57:02.667985712  66-all: info: Initialized successfully: scandir@ obgreet
2022-04-19 15:57:02.667986674  66-all: tracing: Write state file of: mount-run@ obgreet
2022-04-19 15:57:02.667987465  66-all: info: Initialized successfully: mount-run@ obgreet
2022-04-19 15:57:02.667988237  66-all: tracing: Write state file of: boot-user@ obgreet
2022-04-19 15:57:02.667991593  66-all: info: Initialized successfully: boot-user@ obgreet
2022-04-19 15:57:02.667994779  66-all: tracing: reload scandir: /run/66/scandir/0
2022-04-19 15:57:02.668426248  66-all: tracing: sanitize atomic services list...
2022-04-19 15:57:02.668427591  66-all: tracing: start atomic services list ...
2022-04-19 15:57:02.669570654  s6-rc: info: bringing selected services up
2022-04-19 15:57:02.669676352  s6-rc: info: service s6rc-fdholder: starting
2022-04-19 15:57:02.669748508  s6-rc: info: service s6rc-oneshot-runner: starting
2022-04-19 15:57:02.672667421  s6-rc: info: service s6rc-oneshot-runner successfully started
2022-04-19 15:57:02.672729117  s6-rc: info: service setenv@ myUser: starting
2022-04-19 15:57:02.672816651  s6-rc: info: service setenv@ obgreet: starting
2022-04-19 15:57:02.672947286  s6-rc: info: service mount-run@ myUser: starting
2022-04-19 15:57:02.673025222  s6-rc: info: service mount-run@ obgreet: starting
2022-04-19 15:57:02.674431059  s6-rc: info: service s6rc-fdholder successfully started
2022-04-19 15:57:02.674500709  s6-rc: info: service svscan@ myUser-log: starting
2022-04-19 15:57:02.674579517  s6-rc: info: service svscan@ obgreet-log: starting
2022-04-19 15:57:02.674666841  s6-rc: info: service seatd-log: starting
2022-04-19 15:57:02.674740239  s6-rc: info: service greetd-log: starting
2022-04-19 15:57:02.674810100  s6-rc: info: service dbus-log: starting
2022-04-19 15:57:02.677827228  s6-rc: info: service mount-run@ myUser successfully started
2022-04-19 15:57:02.678110379  s6-rc: info: service mount-run@ obgreet successfully started
2022-04-19 15:57:02.678555293  s6-rc: info: service svscan@ obgreet-log successfully started
2022-04-19 15:57:02.678625495  s6-rc: info: service svscan@ myUser-log successfully started
2022-04-19 15:57:02.678816834  s6-rc: info: service seatd-log successfully started
2022-04-19 15:57:02.678919887  s6-rc: info: service seatd: starting
2022-04-19 15:57:02.679048368  s6-rc: info: service greetd-log successfully started
2022-04-19 15:57:02.679061953  s6-rc: info: service dbus-log successfully started
2022-04-19 15:57:02.679140200  s6-rc: info: service dbus: starting
2022-04-19 15:57:02.680022966  s6-rc: info: service seatd successfully started
2022-04-19 15:57:02.680121811  s6-rc: info: service greetd: starting
2022-04-19 15:57:02.681250107  s6-rc: info: service greetd successfully started
2022-04-19 15:57:02.689337824  s6-rc: info: service setenv@ obgreet successfully started
2022-04-19 15:57:02.689408957  s6-rc: info: service svscan@ obgreet: starting
2022-04-19 15:57:02.689611958  s6-rc: info: service setenv@ myUser successfully started
2022-04-19 15:57:02.689663765  s6-rc: info: service svscan@ myUser: starting
2022-04-19 15:57:02.693818757  s6-rc: info: service dbus successfully started
2022-04-19 15:57:02.695648719  s6-rc: info: service svscan@ obgreet successfully started
2022-04-19 15:57:02.696651620  s6-rc: info: service svscan@ myUser successfully started
2022-04-19 15:57:02.696711241  66-all: tracing: Write state file of: setenv@ obgreet
2022-04-19 15:57:02.696723013  66-all: info: Started successfully: setenv@ obgreet
2022-04-19 15:57:02.696744654  66-all: tracing: Write state file of: svscan@ obgreet-log
2022-04-19 15:57:02.696752429  66-all: info: Started successfully: svscan@ obgreet-log
2022-04-19 15:57:02.696759582  66-all: tracing: Write state file of: svscan@ obgreet
2022-04-19 15:57:02.696761385  66-all: info: Started successfully: svscan@ obgreet
2022-04-19 15:57:02.696768499  66-all: tracing: Write state file of: scandir@ obgreet
2022-04-19 15:57:02.696770052  66-all: info: Started successfully: scandir@ obgreet
2022-04-19 15:57:02.696771645  66-all: tracing: Write state file of: mount-run@ obgreet
2022-04-19 15:57:02.696777285  66-all: info: Started successfully: mount-run@ obgreet
2022-04-19 15:57:02.696778548  66-all: tracing: Write state file of: dbus-log
2022-04-19 15:57:02.696779760  66-all: info: Started successfully: dbus-log
2022-04-19 15:57:02.696785240  66-all: tracing: Write state file of: dbus
2022-04-19 15:57:02.696786462  66-all: info: Started successfully: dbus
2022-04-19 15:57:02.696791752  66-all: tracing: Write state file of: seatd-log
2022-04-19 15:57:02.696797132  66-all: info: Started successfully: seatd-log
2022-04-19 15:57:02.696798365  66-all: tracing: Write state file of: seatd
2022-04-19 15:57:02.696803745  66-all: info: Started successfully: seatd
2022-04-19 15:57:02.696805007  66-all: tracing: Write state file of: greetd-log
2022-04-19 15:57:02.696810397  66-all: info: Started successfully: greetd-log
2022-04-19 15:57:02.696815837  66-all: tracing: Write state file of: greetd
2022-04-19 15:57:02.696817060  66-all: info: Started successfully: greetd
2022-04-19 15:57:02.696818342  66-all: tracing: Write state file of: display-manager@ greetd
2022-04-19 15:57:02.696823853  66-all: info: Started successfully: display-manager@ greetd
2022-04-19 15:57:02.696825165  66-all: tracing: Write state file of: console-tracker@ seatd
2022-04-19 15:57:02.696826447  66-all: info: Started successfully: console-tracker@ seatd
2022-04-19 15:57:02.696831858  66-all: tracing: Write state file of: boot-user@ obgreet
2022-04-19 15:57:02.696833140  66-all: info: Started successfully: boot-user@ obgreet
2022-04-19 15:57:02.696834392  66-all: tracing: Write state file of: setenv@ myUser
2022-04-19 15:57:02.696839843  66-all: info: Started successfully: setenv@ myUser
2022-04-19 15:57:02.696841135  66-all: tracing: Write state file of: svscan@ myUser-log
2022-04-19 15:57:02.696842387  66-all: info: Started successfully: svscan@ myUser-log
2022-04-19 15:57:02.696847848  66-all: tracing: Write state file of: svscan@ myUser
2022-04-19 15:57:02.696849100  66-all: info: Started successfully: svscan@ myUser
2022-04-19 15:57:02.696850342  66-all: tracing: Write state file of: scandir@ myUser
2022-04-19 15:57:02.696858938  66-all: info: Started successfully: scandir@ myUser
2022-04-19 15:57:02.696860251  66-all: tracing: Write state file of: mount-run@ myUser
2022-04-19 15:57:02.696861503  66-all: info: Started successfully: mount-run@ myUser
2022-04-19 15:57:02.696862766  66-all: tracing: Write state file of: boot-user@ myUser
2022-04-19 15:57:02.696868586  66-all: info: Started successfully: boot-user@ myUser
2022-04-19 15:57:02.696869969  66-all: tracing: switch atomic services list of: desktop to source
2022-04-19 15:57:02.698378278  66-all: tracing: point symlink: /run/66/state/0/net/servicedirs to /var/lib/66/system/net/servicedirs
2022-04-19 15:57:02.698393115  66-all: info: Initialization aborted -- wpa_supplicant-nl80211@ wlo1-log already initialized
2022-04-19 15:57:02.698394839  66-all: tracing: Write state file of: wpa_supplicant-nl80211@ wlo1-log
2022-04-19 15:57:02.698416139  66-all: info: Initialization aborted -- wpa_supplicant-nl80211@ wlo1 already initialized
2022-04-19 15:57:02.698417561  66-all: tracing: Write state file of: wpa_supplicant-nl80211@ wlo1
2022-04-19 15:57:02.698431938  66-all: tracing: init service: dhcpcd-log
2022-04-19 15:57:02.698438110  66-all: tracing: copy: /var/lib/66/system/net/servicedirs/svc/dhcpcd to /run/66/scandir/0/dhcpcd
2022-04-19 15:57:02.699031753  66-all: tracing: create file: /run/66/scandir/0/dhcpcd/log/down
2022-04-19 15:57:02.699036692  66-all: tracing: create fifo: /run/66/scandir/0/dhcpcd/log/event
2022-04-19 15:57:02.699048304  66-all: tracing: subcribe to fifo: /run/66/scandir/0/dhcpcd/log/event
2022-04-19 15:57:02.699165815  66-all: tracing: init service: dhcpcd
2022-04-19 15:57:02.699173860  66-all: tracing: create file: /run/66/scandir/0/dhcpcd/down
2022-04-19 15:57:02.699185662  66-all: tracing: create fifo: /run/66/scandir/0/dhcpcd/event
2022-04-19 15:57:02.699196252  66-all: tracing: subcribe to fifo: /run/66/scandir/0/dhcpcd/event
2022-04-19 15:57:02.699271012  66-all: tracing: init service: openntpd-log
2022-04-19 15:57:02.699273767  66-all: tracing: copy: /var/lib/66/system/net/servicedirs/svc/openntpd to /run/66/scandir/0/openntpd
2022-04-19 15:57:02.699775037  66-all: tracing: create file: /run/66/scandir/0/openntpd/log/down
2022-04-19 15:57:02.699783042  66-all: tracing: create fifo: /run/66/scandir/0/openntpd/log/event
2022-04-19 15:57:02.699790476  66-all: tracing: subcribe to fifo: /run/66/scandir/0/openntpd/log/event
2022-04-19 15:57:02.699822386  66-all: tracing: init service: openntpd
2022-04-19 15:57:02.699827796  66-all: tracing: create file: /run/66/scandir/0/openntpd/down
2022-04-19 15:57:02.699834799  66-all: tracing: create fifo: /run/66/scandir/0/openntpd/event
2022-04-19 15:57:02.699843305  66-all: tracing: subcribe to fifo: /run/66/scandir/0/openntpd/event
2022-04-19 15:57:02.699865086  66-all: tracing: reload scandir: /run/66/scandir/0
2022-04-19 15:57:02.699876898  66-all: tracing: waiting for events on fifo
2022-04-19 15:57:02.700748092  66-all: tracing: delete down file at: /run/66/scandir/0/dhcpcd/log/down
2022-04-19 15:57:02.700752240  66-all: tracing: delete down file at: /run/66/scandir/0/dhcpcd/down
2022-04-19 15:57:02.700753873  66-all: tracing: delete down file at: /run/66/scandir/0/openntpd/log/down
2022-04-19 15:57:02.700755345  66-all: tracing: delete down file at: /run/66/scandir/0/openntpd/down
2022-04-19 15:57:02.700756738  66-all: tracing: Write state file of: wpa_supplicant-nl80211@ wlo1-log
2022-04-19 15:57:02.700766687  66-all: info: Initialized successfully: wpa_supplicant-nl80211@ wlo1-log
2022-04-19 15:57:02.700768029  66-all: tracing: Write state file of: wpa_supplicant-nl80211@ wlo1
2022-04-19 15:57:02.700769352  66-all: info: Initialized successfully: wpa_supplicant-nl80211@ wlo1
2022-04-19 15:57:02.700770594  66-all: tracing: Write state file of: dhcpcd-log
2022-04-19 15:57:02.700776625  66-all: info: Initialized successfully: dhcpcd-log
2022-04-19 15:57:02.700777888  66-all: tracing: Write state file of: dhcpcd
2022-04-19 15:57:02.700779110  66-all: info: Initialized successfully: dhcpcd
2022-04-19 15:57:02.700780332  66-all: tracing: Write state file of: openntpd-log
2022-04-19 15:57:02.700790792  66-all: info: Initialized successfully: openntpd-log
2022-04-19 15:57:02.700792034  66-all: tracing: Write state file of: openntpd
2022-04-19 15:57:02.700793276  66-all: info: Initialized successfully: openntpd
2022-04-19 15:57:02.701094431  66-all: info: Initialization: no atomic services into tree: net
2022-04-19 15:57:02.701097978  66-all: tracing: reload scandir: /run/66/scandir/0
2022-04-19 15:57:02.701210990  66-all: tracing: sanitize classic services list...
2022-04-19 15:57:02.701214436  66-all: tracing: start classic services list ...
2022-04-19 15:57:02.701342526  66-all: info: Already up: wpa_supplicant-nl80211@ wlo1-log
2022-04-19 15:57:02.701344119  66-all: info: Already up: wpa_supplicant-nl80211@ wlo1
2022-04-19 15:57:02.701540297  66-all: tracing: clean up fifo: /run/66/scandir/0/openntpd/log/event
2022-04-19 15:57:02.701545497  66-all: tracing: subcribe to fifo: /run/66/scandir/0/openntpd/log/event
2022-04-19 15:57:02.701588918  66-all: tracing: clean up fifo: /run/66/scandir/0/openntpd/event
2022-04-19 15:57:02.701593347  66-all: tracing: subcribe to fifo: /run/66/scandir/0/openntpd/event
2022-04-19 15:57:02.701611270  66-all: tracing: clean up fifo: /run/66/scandir/0/dhcpcd/log/event
2022-04-19 15:57:02.701615568  66-all: tracing: subcribe to fifo: /run/66/scandir/0/dhcpcd/log/event
2022-04-19 15:57:02.701632671  66-all: tracing: clean up fifo: /run/66/scandir/0/dhcpcd/event
2022-04-19 15:57:02.701638021  66-all: tracing: subcribe to fifo: /run/66/scandir/0/dhcpcd/event
2022-04-19 15:57:02.701744079  66-all: tracing: send signal: uwU to: /run/66/scandir/0/openntpd/log/supervise
2022-04-19 15:57:02.701749800  66-all: tracing: send signal: u to: /run/66/scandir/0/openntpd/supervise
2022-04-19 15:57:02.701795185  66-all: tracing: send signal: uwU to: /run/66/scandir/0/dhcpcd/log/supervise
2022-04-19 15:57:02.701836322  66-all: tracing: send signal: u to: /run/66/scandir/0/dhcpcd/supervise
2022-04-19 15:57:02.704186449  66-all: info: openntpd-log: started successfully
2022-04-19 15:57:02.704189064  66-all: tracing: Write state file of: openntpd-log
2022-04-19 15:57:02.704195466  66-all: info: openntpd: started successfully
2022-04-19 15:57:02.704196088  66-all: tracing: Write state file of: openntpd
2022-04-19 15:57:02.704198803  66-all: info: dhcpcd-log: started successfully
2022-04-19 15:57:02.704199384  66-all: tracing: Write state file of: dhcpcd-log
2022-04-19 15:57:02.704201908  66-all: info: dhcpcd: started successfully
2022-04-19 15:57:02.704202460  66-all: tracing: Write state file of: dhcpcd
2022-04-19 15:57:02.704390412  66-all: tracing: switch classic service list of: net to source
2022-04-19 15:57:02.706209574  66-all: info: Initialization report: no classic services into tree: myUser
2022-04-19 15:57:02.706828574  66-all: info: Initialization: no atomic services into tree: myUser
2022-04-19 15:57:02.706830498  66-all: tracing: reload scandir: /run/66/scandir/0
2022-04-19 15:57:02.706839645  66-all: warning: uninitialized tree: myUser
2022-04-19 15:57:02.707137504  s6-rc: info: service all-Runtime successfully started
2022-04-19 15:57:02.707272707  s6-rc: info: service tty-rc@ tty2: starting
2022-04-19 15:57:02.707369910  s6-rc: info: service tty-rc@ tty1: starting
2022-04-19 15:57:02.708742093  s6-rc: info: service tty-rc@ tty1 successfully started
2022-04-19 15:57:02.708864212  s6-rc: info: service tty-rc@ tty2 successfully started
2022-04-19 15:57:02.708967956  66-dbctl: tracing: Write state file of: system-hostname
2022-04-19 15:57:02.708987172  66-dbctl: info: Started successfully: system-hostname
2022-04-19 15:57:02.708988174  66-dbctl: tracing: Write state file of: mount-run
2022-04-19 15:57:02.708991921  66-dbctl: info: Started successfully: mount-run
2022-04-19 15:57:02.708992733  66-dbctl: tracing: Write state file of: populate-run
2022-04-19 15:57:02.709002692  66-dbctl: info: Started successfully: populate-run
2022-04-19 15:57:02.709003443  66-dbctl: tracing: Write state file of: mount-tmp
2022-04-19 15:57:02.709010536  66-dbctl: info: Started successfully: mount-tmp
2022-04-19 15:57:02.709011388  66-dbctl: tracing: Write state file of: populate-tmp
2022-04-19 15:57:02.709014784  66-dbctl: info: Started successfully: populate-tmp
2022-04-19 15:57:02.709015596  66-dbctl: tracing: Write state file of: mount-proc
2022-04-19 15:57:02.709022729  66-dbctl: info: Started successfully: mount-proc
2022-04-19 15:57:02.709023591  66-dbctl: tracing: Write state file of: mount-sys
2022-04-19 15:57:02.709026857  66-dbctl: info: Started successfully: mount-sys
2022-04-19 15:57:02.709030113  66-dbctl: tracing: Write state file of: populate-sys
2022-04-19 15:57:02.709033309  66-dbctl: info: Started successfully: populate-sys
2022-04-19 15:57:02.709036565  66-dbctl: tracing: Write state file of: mount-dev
2022-04-19 15:57:02.709039691  66-dbctl: info: Started successfully: mount-dev
2022-04-19 15:57:02.709042917  66-dbctl: tracing: Write state file of: mount-pts
2022-04-19 15:57:02.709046223  66-dbctl: info: Started successfully: mount-pts
2022-04-19 15:57:02.709049479  66-dbctl: tracing: Write state file of: mount-shm
2022-04-19 15:57:02.709052705  66-dbctl: info: Started successfully: mount-shm
2022-04-19 15:57:02.709053477  66-dbctl: tracing: Write state file of: populate-dev
2022-04-19 15:57:02.709061201  66-dbctl: info: Started successfully: populate-dev
2022-04-19 15:57:02.709061983  66-dbctl: tracing: Write state file of: mount-cgroups
2022-04-19 15:57:02.709068946  66-dbctl: info: Started successfully: mount-cgroups
2022-04-19 15:57:02.709069707  66-dbctl: tracing: Write state file of: 00
2022-04-19 15:57:02.709076710  66-dbctl: info: Started successfully: 00
2022-04-19 15:57:02.709077522  66-dbctl: tracing: Write state file of: system-hwclock
2022-04-19 15:57:02.709084525  66-dbctl: info: Started successfully: system-hwclock
2022-04-19 15:57:02.709085307  66-dbctl: tracing: Write state file of: modules-kernel
2022-04-19 15:57:02.709093131  66-dbctl: info: Started successfully: modules-kernel
2022-04-19 15:57:02.709093943  66-dbctl: tracing: Write state file of: system-random
2022-04-19 15:57:02.709100715  66-dbctl: info: Started successfully: system-random
2022-04-19 15:57:02.709101447  66-dbctl: tracing: Write state file of: modules-system
2022-04-19 15:57:02.709107408  66-dbctl: info: Started successfully: modules-system
2022-04-19 15:57:02.709108229  66-dbctl: tracing: Write state file of: system-sysctl
2022-04-19 15:57:02.709114241  66-dbctl: info: Started successfully: system-sysctl
2022-04-19 15:57:02.709122556  66-dbctl: tracing: Write state file of: udevd-log
2022-04-19 15:57:02.709129369  66-dbctl: info: Started successfully: udevd-log
2022-04-19 15:57:02.709135250  66-dbctl: tracing: Write state file of: udevd
2022-04-19 15:57:02.709142123  66-dbctl: info: Started successfully: udevd
2022-04-19 15:57:02.709142945  66-dbctl: tracing: Write state file of: udevadm
2022-04-19 15:57:02.709148926  66-dbctl: info: Started successfully: udevadm
2022-04-19 15:57:02.709149757  66-dbctl: tracing: Write state file of: system-fontnkey
2022-04-19 15:57:02.709156680  66-dbctl: info: Started successfully: system-fontnkey
2022-04-19 15:57:02.709157432  66-dbctl: tracing: Write state file of: all-Mount
2022-04-19 15:57:02.709163243  66-dbctl: info: Started successfully: all-Mount
2022-04-19 15:57:02.709164044  66-dbctl: tracing: Write state file of: system-fsck
2022-04-19 15:57:02.709170176  66-dbctl: info: Started successfully: system-fsck
2022-04-19 15:57:02.709171007  66-dbctl: tracing: Write state file of: mount-fstab
2022-04-19 15:57:02.709176578  66-dbctl: info: Started successfully: mount-fstab
2022-04-19 15:57:02.709177369  66-dbctl: tracing: Write state file of: all-System
2022-04-19 15:57:02.709182869  66-dbctl: info: Started successfully: all-System
2022-04-19 15:57:02.709183621  66-dbctl: tracing: Write state file of: mount-rw
2022-04-19 15:57:02.709189221  66-dbctl: info: Started successfully: mount-rw
2022-04-19 15:57:02.709190033  66-dbctl: tracing: Write state file of: mount-netfs
2022-04-19 15:57:02.709195313  66-dbctl: info: Started successfully: mount-netfs
2022-04-19 15:57:02.709198669  66-dbctl: tracing: Write state file of: local-loop
2022-04-19 15:57:02.709202266  66-dbctl: info: Started successfully: local-loop
2022-04-19 15:57:02.709205532  66-dbctl: tracing: Write state file of: local-sethostname
2022-04-19 15:57:02.709208828  66-dbctl: info: Started successfully: local-sethostname
2022-04-19 15:57:02.709209620  66-dbctl: tracing: Write state file of: local-time
2022-04-19 15:57:02.709216122  66-dbctl: info: Started successfully: local-time
2022-04-19 15:57:02.709216923  66-dbctl: tracing: Write state file of: local-authfiles
2022-04-19 15:57:02.709223506  66-dbctl: info: Started successfully: local-authfiles
2022-04-19 15:57:02.709224307  66-dbctl: tracing: Write state file of: local-tmpfiles
2022-04-19 15:57:02.709230519  66-dbctl: info: Started successfully: local-tmpfiles
2022-04-19 15:57:02.709231250  66-dbctl: tracing: Write state file of: local-dmesg
2022-04-19 15:57:02.709237833  66-dbctl: info: Started successfully: local-dmesg
2022-04-19 15:57:02.709238604  66-dbctl: tracing: Write state file of: all-Local
2022-04-19 15:57:02.709245347  66-dbctl: info: Started successfully: all-Local
2022-04-19 15:57:02.709246118  66-dbctl: tracing: Write state file of: all-Runtime
2022-04-19 15:57:02.709256568  66-dbctl: info: Started successfully: all-Runtime
2022-04-19 15:57:02.709257990  66-dbctl: tracing: Write state file of: All
2022-04-19 15:57:02.709268320  66-dbctl: info: Started successfully: All
2022-04-19 15:57:02.709275383  66-dbctl: tracing: Write state file of: tty-rc@ tty1
2022-04-19 15:57:02.709282647  66-dbctl: info: Started successfully: tty-rc@ tty1
2022-04-19 15:57:02.709288247  66-dbctl: tracing: Write state file of: tty-rc@ tty2
2022-04-19 15:57:02.709294799  66-dbctl: info: Started successfully: tty-rc@ tty2
2022-04-19 15:57:02.709295611  66-dbctl: tracing: Write state file of: boot@ system
2022-04-19 15:57:02.709301943  66-dbctl: info: Started successfully: boot@ system
Your boot sequence seems correct now.
So now, your audio works or not?
Unfortunately, no. 
> 66-intree -z -g audio
Name         : audio
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : no
Allowed      : myUser
Symlinks     : svc->source db->source
Contents     : /
               ├─(0,Disabled,longrun) pulseaudio-log
               ├─(1263,Enabled,longrun) pipewire-media-session-log
               ├─(1264,Enabled,longrun) pipewire-log
               ├─(19763,Enabled,longrun) pipewire
               ├─(1262,Enabled,longrun) pipewire-pulse-log
               ├─(19771,Enabled,longrun) pipewire-pulse
               ├─(19770,Enabled,longrun) pipewire-media-session
               └─(0,Disabled,longrun) pulseaudio

> PULSE_LOG=4 pactl info -vvv
Parsing configuration file '/etc/pulse/client.conf'
/etc/pulse/client.conf.d does not exist, ignoring.
Using shared memfd memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65472
Trying to connect to /run/users/1000/pulse/native...
connect(): No such file or directory (2)
Trying to connect to /var/run/pulse/native...
connect(): No such file or directory (2)
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
At least you dont need to use 66-start anymore to get those services up...
Do you have XDG_RUNTIME=!yes in the file: # 66-env -t boot-user boot-user@ myUser?

If so, also try installing&starting xdg-user-dirs-66serv and started it alongside pipewire related services.
Pretty sure the command '66-env -t boot-user boot-user@ myUser' won't work since Galeano told me to run the command '66-tree -R boot-user', which would remove the boot-user tree at the administrator level. To make sure though, I did it anyway, both as myUser (obviously fake username) and as sudo.
> 66-env -t boot-user boot-user@ myUser
66-env: fatal: unable to find tree: /home/myUser/.66/system/boot-user: No such file or directory
> sudo !!
66-env: fatal: unable to find tree: /var/lib/66/system/boot-user: No such file or directory
I did find boot-user as a service under a desktop tree though: 
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(288,Enabled,classic) tty-earlier@ 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
               ├─(333,Enabled,longrun) udevd-log
               ├─(507,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) 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
               ├─(up,Enabled,oneshot) local-dmesg
               ├─(up,Enabled,bundle) all-Local
               ├─(up,Enabled,oneshot) all-Runtime
               ├─(up,Enabled,bundle) All
               ├─(976,Enabled,longrun) tty-rc@ tty1
               ├─(977,Enabled,longrun) tty-rc@ tty2
               └─(up,Enabled,module) boot@ system

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(825,Enabled,classic) cupsd-log
               ├─(824,Enabled,classic) wpa_supplicant-nl80211@ wlo1-log
               ├─(26372,Enabled,classic) wpa_supplicant-nl80211@ wlo1
               └─(826,Enabled,classic) cupsd

Name         : desktop
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) setenv@ obgreet
               ├─(887,Enabled,longrun) svscan@ obgreet-log
               ├─(948,Enabled,longrun) svscan@ obgreet
               ├─(up,Enabled,module) scandir@ obgreet
               ├─(up,Enabled,oneshot) mount-run@ obgreet
               ├─(889,Enabled,longrun) dbus-log
               ├─(904,Enabled,longrun) dbus
               ├─(888,Enabled,longrun) seatd-log
               ├─(902,Enabled,longrun) seatd
               ├─(890,Enabled,longrun) greetd-log
               ├─(0,Enabled,longrun) greetd
               ├─(up,Enabled,module) display-manager@ greetd
               ├─(up,Enabled,module) console-tracker@ seatd
               ├─(up,Enabled,module) boot-user@ obgreet
               ├─(up,Enabled,oneshot) setenv@ myUser
               ├─(882,Enabled,longrun) svscan@ myUser-log
               ├─(949,Enabled,longrun) svscan@ myUser
               ├─(up,Enabled,module) scandir@ myUser
               ├─(up,Enabled,oneshot) mount-run@ myUser
               └─(up,Enabled,module) [b]boot-user@ myUser[/b]

Name         : net
Initialized  : yes
Enabled      : yes
Starts after : root desktop
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(964,Enabled,classic) openntpd-log
               ├─(963,Enabled,classic) openntpd
               ├─(965,Enabled,classic) dhcpcd-log
               ├─(824,Enabled,classic) wpa_supplicant-nl80211@ wlo1-log
               ├─(966,Enabled,classic) dhcpcd
               ├─(26372,Enabled,classic) wpa_supplicant-nl80211@ wlo1
               ├─(0,Disabled,classic) wpa_supplicant-log
               └─(0,Disabled,classic) wpa_supplicant

Name         : myUser
Initialized  : no
Enabled      : yes
Starts after : root desktop net
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               └─None

> sudo 66-env -t desktop -e vim boot-user@ myUser
# # Uncomment it to use a display manager.
# # Can be any display manager as long as the
# # corresponding frontend file exist on your system
# # e.g sddm,lightdm,...
# # It also prepare the .xsession file.

# DISPLAY_MANAGER=sddm

# # Uncomment it to use a console tracker.
# # Can be any console tracker as long as the
# # corresponding frontend file exist on your system
# # e.g consolekit,elogind,...

# CONSOLE_TRACKER=consolekit

# # Create and mount the XDG_RUNTIME directory
# # at /run/user/myUser [yes|no]

XDG_RUNTIME=!yes

# # Command to use in your .xinitrc
# # to launch your desktop e.g.: openbox-session.
# # If commented the .xinitrc file is not configured.

# DESKTOP_CMDLINE=!jwm
I think I have xdg-user-dirs installed as part of a graphics tree on the user level.
> pacman -Ql xdg-user-dirs-66serv
xdg-user-dirs-66serv /usr/
xdg-user-dirs-66serv /usr/lib/
xdg-user-dirs-66serv /usr/lib/66/
xdg-user-dirs-66serv /usr/lib/66/service/
xdg-user-dirs-66serv /usr/lib/66/service/xdg-user-dirs
xdg-user-dirs-66serv /usr/share/
xdg-user-dirs-66serv /usr/share/licenses/
xdg-user-dirs-66serv /usr/share/licenses/xdg-user-dirs-66serv/
xdg-user-dirs-66serv /usr/share/licenses/xdg-user-dirs-66serv/LICENSE

> 66-intree -z -g
Name         : audio
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : no
Allowed      : myUser
Symlinks     : svc->source db->source
Contents     : /
               ├─(0,Disabled,longrun) pulseaudio-log
               ├─(1263,Enabled,longrun) pipewire-media-session-log
               ├─(1264,Enabled,longrun) pipewire-log
               ├─(19763,Enabled,longrun) pipewire
               ├─(1262,Enabled,longrun) pipewire-pulse-log
               ├─(19771,Enabled,longrun) pipewire-pulse
               ├─(19770,Enabled,longrun) pipewire-media-session
               └─(0,Disabled,longrun) pulseaudio

Name         : graphics
Initialized  : yes
Enabled      : yes
Starts after : audio
Current      : no
Allowed      : myUser
Symlinks     : svc->source db->source
Contents     : /
               ├─(1211,Enabled,longrun) dbus-session@ myUser-log
               ├─(up,Enabled,oneshot) xdg-user-dirs
               └─(1215,Enabled,longrun) dbus-session@ myUser
Looks like there are conflicting boot-user modules in your desktop tree : boot-user@ obgreet & boot-user@ myUser.... I think there should only be one- someone correct me if im wrong.
XDG_RUNTIME_DIR does apear to be set though. 
echo $XDG_RUNTIME_DIR
/run/users/1000
I think that should be the variable that service xdg-runtime-dirs sets, but I might be wrong about that.

Powered by Obarun