There was initially an error with the
# 66-disable -t boot tty12 All
command (nothing happened), didn't take note of it, since I believed it wasn't too important. Deleted and remade boot with
# 66-tree -R boot
# 66-tree -n boot
# 66-enable -C -F -t boot boot@ cyberia
# 66-env -t boot boot@ cyberia
# 66-enable -F -t boot boot@ cyberia
However, startx now fails. Returning errors regarding inability to find 66-which and 66-all. Nothing about this is reported in the Xorg log file either, since the errors are shown after logging ends.

66-intree -gv4 boot
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               |-(390,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,bundle) all-Mount
               |-(up,Enabled,oneshot) system-hwclock
               |-(up,Enabled,oneshot) modules-kernel
               |-(up,Enabled,oneshot) system-random
               |-(up,Enabled,oneshot) modules-system
               |-(up,Enabled,oneshot) system-sysctl
               |-(434,Enabled,longrun) udevd-log
               |-(594,Enabled,longrun) udevd
               |-(up,Enabled,oneshot) udevadm
               |-(up,Enabled,oneshot) system-fontnkey
               |-(up,Enabled,oneshot) system-fsck
               |-(up,Enabled,oneshot) mount-fstab
               |-(up,Enabled,bundle) all-System
               |-(up,Enabled,oneshot) mount-rw
               |-(up,Enabled,oneshot) mount-swap
               |-(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
               |-(4005,Enabled,longrun) tty-rc@ tty2
               |-(3997,Enabled,longrun) tty-rc@ tty1
               |-(1331,Enabled,longrun) tty-rc@ tty3
               `-(up,Enabled,module) boot@ cyberia
66-intree -gv4 net
Name         : boot-user
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               |-(up,Enabled,oneshot) setenv@ magicalsenpai
               |-(1040,Enabled,longrun) svscan@ magicalsenpai-log
               |-(1076,Enabled,longrun) svscan@ magicalsenpai
               |-(up,Enabled,module) scandir@ magicalsenpai
               |-(up,Enabled,oneshot) mount-run@ magicalsenpai
               |-(1041,Enabled,longrun) consolekit-log
               |-(1048,Enabled,longrun) consolekit
               |-(up,Enabled,module) console-tracker@ consolekit
               `-(up,Enabled,module) boot-user@ magicalsenpai
/run/66/log/0/current (verbosity 4)
2021-02-14 14:42:21.763321104  66-all(src/lib66/svc_init.c: svc_init(): 98): tracing: init service: clamd
2021-02-14 14:42:21.763321936  66-all(src/lib66/svc_init.c: svc_init(): 143): tracing: create file: /run/66/scandir/0/clamd/down
2021-02-14 14:42:21.763322607  66-all(src/lib66/svc_init.c: svc_init(): 151): tracing: create fifo: /run/66/scandir/0/clamd/event
2021-02-14 14:42:21.763323218  66-all(src/lib66/svc_init.c: svc_init(): 157): tracing: subcribe to fifo: /run/66/scandir/0/clamd/event
2021-02-14 14:42:21.763329971  66-all(src/lib66/svc_init.c: svc_init(): 169): tracing: reload scandir: /run/66/scandir/0
2021-02-14 14:42:21.763332826  66-all(src/lib66/svc_init.c: svc_init(): 176): tracing: waiting for events on fifo
2021-02-14 14:42:21.763699544  66-all(src/lib66/svc_init.c: svc_init(): 182): tracing: delete down file at: /run/66/scandir/0/nordvpnd/log/down
2021-02-14 14:42:21.763702329  66-all(src/lib66/svc_init.c: svc_init(): 182): tracing: delete down file at: /run/66/scandir/0/nordvpnd/down
2021-02-14 14:42:21.763704784  66-all(src/lib66/svc_init.c: svc_init(): 182): tracing: delete down file at: /run/66/scandir/0/clamd/log/down
2021-02-14 14:42:21.763705405  66-all(src/lib66/svc_init.c: svc_init(): 182): tracing: delete down file at: /run/66/scandir/0/clamd/down
2021-02-14 14:42:21.763707770  66-all(src/lib66/svc_init.c: svc_init(): 192): tracing: Write state file of: nordvpnd-log
2021-02-14 14:42:21.763712128  66-all(src/lib66/svc_init.c: svc_init(): 198): info: Initialized successfully: nordvpnd-log
2021-02-14 14:42:21.763712759  66-all(src/lib66/svc_init.c: svc_init(): 192): tracing: Write state file of: nordvpnd
2021-02-14 14:42:21.763715143  66-all(src/lib66/svc_init.c: svc_init(): 198): info: Initialized successfully: nordvpnd
2021-02-14 14:42:21.763715755  66-all(src/lib66/svc_init.c: svc_init(): 192): tracing: Write state file of: clamd-log
2021-02-14 14:42:21.763718089  66-all(src/lib66/svc_init.c: svc_init(): 198): info: Initialized successfully: clamd-log
2021-02-14 14:42:21.763718690  66-all(src/lib66/svc_init.c: svc_init(): 192): tracing: Write state file of: clamd
2021-02-14 14:42:21.763721034  66-all(src/lib66/svc_init.c: svc_init(): 198): info: Initialized successfully: clamd
2021-02-14 14:42:21.763875043  66-all(src/lib66/rc_init.c: rc_init(): 84): info: Initialization: no atomic services into tree: security
2021-02-14 14:42:21.763875664  66-all(src/lib66/ssexec_all.c: ssexec_all(): 350): tracing: reload scandir: /run/66/scandir/0
2021-02-14 14:42:21.763926850  66-all(src/lib66/ssexec_start.c: ssexec_start(): 344): tracing: sanitize classic services list...
2021-02-14 14:42:21.763927482  66-all(src/lib66/ssexec_start.c: ssexec_start(): 347): tracing: start classic services list ...
2021-02-14 14:42:21.764176829  66-all(src/lib66/svc_init_pipe.c: svc_init_pipe(): 53): tracing: clean up fifo: /run/66/scandir/0/clamd/log/event
2021-02-14 14:42:21.764181488  66-all(src/lib66/svc_init_pipe.c: svc_init_pipe(): 57): tracing: subcribe to fifo: /run/66/scandir/0/clamd/log/event
2021-02-14 14:42:21.764223797  66-all(src/lib66/svc_init_pipe.c: svc_init_pipe(): 53): tracing: clean up fifo: /run/66/scandir/0/clamd/event
2021-02-14 14:42:21.764226372  66-all(src/lib66/svc_init_pipe.c: svc_init_pipe(): 57): tracing: subcribe to fifo: /run/66/scandir/0/clamd/event
2021-02-14 14:42:21.764243204  66-all(src/lib66/svc_init_pipe.c: svc_init_pipe(): 53): tracing: clean up fifo: /run/66/scandir/0/nordvpnd/log/event
2021-02-14 14:42:21.764245588  66-all(src/lib66/svc_init_pipe.c: svc_init_pipe(): 57): tracing: subcribe to fifo: /run/66/scandir/0/nordvpnd/log/event
2021-02-14 14:42:21.764259474  66-all(src/lib66/svc_init_pipe.c: svc_init_pipe(): 53): tracing: clean up fifo: /run/66/scandir/0/nordvpnd/event
2021-02-14 14:42:21.764261859  66-all(src/lib66/svc_init_pipe.c: svc_init_pipe(): 57): tracing: subcribe to fifo: /run/66/scandir/0/nordvpnd/event
2021-02-14 14:42:21.764320248  66-all(src/lib66/ssexec_svctl.c: svc_writectl(): 425): tracing: send signal: uwU to: /run/66/scandir/0/clamd/log/supervise
2021-02-14 14:42:21.764349212  66-all(src/lib66/ssexec_svctl.c: svc_writectl(): 425): tracing: send signal: u to: /run/66/scandir/0/clamd/supervise
2021-02-14 14:42:21.764385781  66-all(src/lib66/ssexec_svctl.c: svc_writectl(): 425): tracing: send signal: uwU to: /run/66/scandir/0/nordvpnd/log/supervise
2021-02-14 14:42:21.764413132  66-all(src/lib66/ssexec_svctl.c: svc_writectl(): 425): tracing: send signal: u to: /run/66/scandir/0/nordvpnd/supervise
2021-02-14 14:42:21.765831252  66-all(src/lib66/ssexec_svctl.c: announce(): 267): info: clamd-log: started successfully
2021-02-14 14:42:21.765831883  66-all(src/lib66/ssexec_svctl.c: write_state(): 240): tracing: Write state file of: clamd-log
2021-02-14 14:42:21.765839748  66-all(src/lib66/ssexec_svctl.c: announce(): 267): info: clamd: started successfully
2021-02-14 14:42:21.765840339  66-all(src/lib66/ssexec_svctl.c: write_state(): 240): tracing: Write state file of: clamd
2021-02-14 14:42:21.765843084  66-all(src/lib66/ssexec_svctl.c: announce(): 267): info: nordvpnd-log: started successfully
2021-02-14 14:42:21.765845458  66-all(src/lib66/ssexec_svctl.c: write_state(): 240): tracing: Write state file of: nordvpnd-log
2021-02-14 14:42:21.765847823  66-all(src/lib66/ssexec_svctl.c: announce(): 267): info: nordvpnd: started successfully
2021-02-14 14:42:21.765848414  66-all(src/lib66/ssexec_svctl.c: write_state(): 240): tracing: Write state file of: nordvpnd
2021-02-14 14:42:21.765907064  66-all(src/lib66/ssexec_start.c: ssexec_start(): 359): tracing: switch classic service list of: security to source
2021-02-14 14:42:21.766118220  s6-rc: info: service all-Runtime successfully started
2021-02-14 14:42:21.766165980  s6-rc: info: service tty-rc@ tty3: starting
2021-02-14 14:42:21.766208048  s6-rc: info: service tty-rc@ tty2: starting
2021-02-14 14:42:21.766256630  s6-rc: info: service tty-rc@ tty1: starting
2021-02-14 14:42:21.767009461  s6-rc: info: service tty-rc@ tty3 successfully started
2021-02-14 14:42:21.767102306  s6-rc: info: service tty-rc@ tty1 successfully started
2021-02-14 14:42:21.767238180  s6-rc: info: service tty-rc@ tty2 successfully started
2021-02-14 14:42:21.767300958  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: system-hostname
2021-02-14 14:42:21.767309224  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: system-hostname
2021-02-14 14:42:21.767309755  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-run
2021-02-14 14:42:21.767314974  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-run
2021-02-14 14:42:21.767315475  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: populate-run
2021-02-14 14:42:21.767320755  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: populate-run
2021-02-14 14:42:21.767321246  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-tmp
2021-02-14 14:42:21.767326195  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-tmp
2021-02-14 14:42:21.767326686  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: populate-tmp
2021-02-14 14:42:21.767331756  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: populate-tmp
2021-02-14 14:42:21.767332237  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-proc
2021-02-14 14:42:21.767337797  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-proc
2021-02-14 14:42:21.767338278  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-sys
2021-02-14 14:42:21.767343758  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-sys
2021-02-14 14:42:21.767344239  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: populate-sys
2021-02-14 14:42:21.767349529  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: populate-sys
2021-02-14 14:42:21.767350030  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-dev
2021-02-14 14:42:21.767353216  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-dev
2021-02-14 14:42:21.767355460  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-pts
2021-02-14 14:42:21.767360630  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-pts
2021-02-14 14:42:21.767361131  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-shm
2021-02-14 14:42:21.767366301  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-shm
2021-02-14 14:42:21.767366792  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: populate-dev
2021-02-14 14:42:21.767372051  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: populate-dev
2021-02-14 14:42:21.767372542  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-cgroups
2021-02-14 14:42:21.767377522  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-cgroups
2021-02-14 14:42:21.767378003  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: 00
2021-02-14 14:42:21.767383282  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: 00
2021-02-14 14:42:21.767383783  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: all-Mount
2021-02-14 14:42:21.767388863  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: all-Mount
2021-02-14 14:42:21.767389354  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: system-hwclock
2021-02-14 14:42:21.767394734  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: system-hwclock
2021-02-14 14:42:21.767395235  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: modules-kernel
2021-02-14 14:42:21.767400324  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: modules-kernel
2021-02-14 14:42:21.767400805  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: system-random
2021-02-14 14:42:21.767405945  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: system-random
2021-02-14 14:42:21.767406466  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: modules-system
2021-02-14 14:42:21.767411555  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: modules-system
2021-02-14 14:42:21.767412056  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: system-sysctl
2021-02-14 14:42:21.767417537  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: system-sysctl
2021-02-14 14:42:21.767422426  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: udevd-log
2021-02-14 14:42:21.767427976  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: udevd-log
2021-02-14 14:42:21.767430180  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: udevd
2021-02-14 14:42:21.767436943  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: udevd
2021-02-14 14:42:21.767437434  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: udevadm
2021-02-14 14:42:21.767443535  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: udevadm
2021-02-14 14:42:21.767444157  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: system-fontnkey
2021-02-14 14:42:21.767447082  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: system-fontnkey
2021-02-14 14:42:21.767450879  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: system-fsck
2021-02-14 14:42:21.767453765  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: system-fsck
2021-02-14 14:42:21.767456279  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-fstab
2021-02-14 14:42:21.767458974  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-fstab
2021-02-14 14:42:21.767461509  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: all-System
2021-02-14 14:42:21.767466819  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: all-System
2021-02-14 14:42:21.767467510  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-rw
2021-02-14 14:42:21.767470185  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-rw
2021-02-14 14:42:21.767472750  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-swap
2021-02-14 14:42:21.767475205  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-swap
2021-02-14 14:42:21.767477249  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-netfs
2021-02-14 14:42:21.767482428  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: mount-netfs
2021-02-14 14:42:21.767482919  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: local-loop
2021-02-14 14:42:21.767487989  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: local-loop
2021-02-14 14:42:21.767488490  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: local-sethostname
2021-02-14 14:42:21.767493659  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: local-sethostname
2021-02-14 14:42:21.767494150  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: local-time
2021-02-14 14:42:21.767499050  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: local-time
2021-02-14 14:42:21.767499530  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: local-authfiles
2021-02-14 14:42:21.767504600  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: local-authfiles
2021-02-14 14:42:21.767505101  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: local-tmpfiles
2021-02-14 14:42:21.767510110  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: local-tmpfiles
2021-02-14 14:42:21.767510611  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: local-dmesg
2021-02-14 14:42:21.767515781  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: local-dmesg
2021-02-14 14:42:21.767516262  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: all-Local
2021-02-14 14:42:21.767521772  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: all-Local
2021-02-14 14:42:21.767522253  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: all-Runtime
2021-02-14 14:42:21.767527162  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: all-Runtime
2021-02-14 14:42:21.767527663  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: All
2021-02-14 14:42:21.767532743  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: All
2021-02-14 14:42:21.767534797  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: tty-rc@ tty2
2021-02-14 14:42:21.767541169  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: tty-rc@ tty2
2021-02-14 14:42:21.767543343  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: tty-rc@ tty1
2021-02-14 14:42:21.767549805  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: tty-rc@ tty1
2021-02-14 14:42:21.767551889  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: tty-rc@ tty3
2021-02-14 14:42:21.767558130  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: tty-rc@ tty3
2021-02-14 14:42:21.767558611  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: boot@ cyberia
2021-02-14 14:42:21.767563761  66-dbctl(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Started successfully: boot@ cyberia
~/.xinitrc
# !/usr/bin/bash

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

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

66-all up

# # Try consolekit
if 66-which -q ck-launch-session; then
        cmd="exec ck-launch-session $@ "
else
        cmd="exec $@ "
fi

# # Select the session to start
${cmd} dwm
/etc/66/init.conf
VERBOSITY=4
LIVE=/run/66
PATH=/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin
TREE=boot
RCINIT=/etc/66/rc.init
RCSHUTDOWN=/etc/66/rc.shutdown
RCSHUTDOWNFINAL=/etc/66/rc.shutdown.final
UMASK=0022
RESCAN=0
CONTAINER=0
RCINIT_CONTAINER=/etc/66/rc.init.container
CATCHLOG=1
Returning errors regarding inability to find 66-which and 66-all
Huh!!
66-which is a part of the 66-tool package and 66-all come with the 66 package. Both are present is the respective package
 % sudo pacman -Fl 66-tools | grep 66-which
66-tools usr/bin/66-which
66-tools usr/share/doc/66-tools/0.0.7.1/66-which.html
66-tools usr/share/man/man1/66-which.1.gz

% sudo pacman -Fl 66 | grep 66-all   
66 usr/bin/66-all
66 usr/share/doc/66/0.6.1.1/66-all.html
66 usr/share/man/man1/66-all.1.gz
This is really strange. Can please you check the output of pacman -Fyl for 66 and 66-tools like me?
Had to run sudo pacman -Fy, but the output now is the same as yours
% sudo pacman -Fl 66-tools | grep 66-which
66-tools usr/bin/66-which
66-tools usr/share/doc/66-tools/0.0.7.1/66-which.html
66-tools usr/share/man/man1/66-which.1.gz

% sudo pacman -Fl 66 | grep 66-all
66 usr/bin/66-all
66 usr/share/doc/66/0.6.1.1/66-all.html
66 usr/share/man/man1/66-all.1.gz
Logged out and logged back in, same issue.
magicalsenpai wroteThere was initially an error with the
# 66-disable -t boot tty12 All
command (nothing happened)
66-disable All will have an effect on next boot, not immediately, even with -S since most of what makes All are one shots that are already done. 66-disable tty12 SHOULD be an error since there was no tty12 for 4-5 versions back, when tty@ tty12 replaced it.

But you didn't provide the output of the error.
Now tty@ tty12 is replaced by tty-earlier@ tty12

I am interested in "why" do the pids of tty-rc@ tty1 tty-rc@ tty2 are so much higher than tty-rc@ tty3, which appears as a more normal pid. I have seen some of this on my system as well and trying to understand what is happening. Maybe I should add logging into the tty-rc service file that may give me clues.
what's happen if you prefix your 66-all and 66-which command on your .xinitrc with the default path?
/usr/bin/66-all
/usr/bin/66-which
EDIT:
Please, give the output of
% ls -1 /home/magicalsenpai/.66/conf/svscan@ magicalsenpai
and the contents of each file inside this directory.
Also,
# 66-inservice setenv@ magicalsenpai
# 66-inservice svscan@ magicalsenpai
% ls -1 /home/magicalsenpai/.66/conf/svscan@ magicalsenpai
svscan@ magicalsenpai
zzz_userdefined
Contents:
svscan@ magicalsenpai
HOME=/home/magicalsenpai
LOGNAME=magicalsenpai
USER=magicalsenpai
PATH=/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin
SHELL=/usr/bin/zsh
DISPLAY=:0
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
XDG_RUNTIME_DIR=/run/user/1000
XDG_CACHE_HOME=/home/magicalsenpai/.cache
XDG_CONFIG_HOME=/home/magicalsenpai/.config
XDG_DATA_HOME=/home/magicalsenpai/.local/share
XDG_DATA_DIRS=/home/magicalsenpai/.local/share:/usr/local/share:/usr/share
XDG_SESSION_CLASS=user
zzz_userdefined
PATH=$PATH:/home/magicalsenpai/.local/bin
IPFS_PATH=/home/magicalsenpai/.config/ipfs
ZDOTDIR=/home/magicalsenpai/.config/oh-my-zsh
GNUPGHOME=/home/magicalsenpai/.config/gnupg
WEECHAT_HOME=/home/magicalsenpai/.config/weechat

CCACHE_DIR=/home/magicalsenpai/.cache/ccache

RUSTUP_HOME=/home/magicalsenpai/.local/share/rustup
CARGO_HOME=/home/magicalsenpai/.local/share/cargo

GOPATH=/home/magicalsenpai/.local/lib/go
GOROOT=/usr/lib/go

NVIM_LOG_FILE=/home/magicalsenpai/.logs/nvim/log
I added the full paths and despite it *technically* working (no error messages) and X starting, my keybindings no longer work. Even when running
% startx /usr/local/bin/dwm
, like before the change to my .xinitrc, the keybindings fail.

I was planning on holding off on this until the end of the week (when my pre-66 update backup would be deleted). But I can't comfortably use my desktop like this. So I'm gonna timeshift back and attempt the upgrade again.

EDIT: The issue is persisting beyond even a timeshift. Very strange.
did similar thing way back when i started using obarun, and it ddnt go well on my end, exporting duplicate env vars instead.
I ended up just using a separate file from my own environment settings (zzz_userdefined in ur example) and source it after 66-all up runs, either in .xinitrc or .xsession (if using lightdm or other dm).

e.g.
this would get sourced correctly and will end up as a duplicate path, at least on my end
PATH=$PATH:/home/magicalsenpai/.local/bin
I'm surprised that your environment file worked before the update.
You cannot set your PATH like you do. PATH=$PATH:/rep is a sh/bash/zsh/... thing. I mean the sh interpreter will recognize the $PATH term and change it by the value of the variable. But execl-envfile do not know anything about that and the $PATH will be interpreted as it. So, if you echoing your PATH variable it will be literally PATH=$PATH:/home/magicalsenpai/.local/bin and not PATH=/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin:/home/magicalsenpai/.local/bin like you expect.
Well at your zzz_userdefined set
PATH=/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin:/home/magicalsenpai/.local/bin

Do you have enabled again the boot-user@ service?
and please like i answered you, show me the output of
# 66-inservice setenv@ magicalsenpai
# 66-inservice svscan@ magicalsenpai
negative wrote I ended up just using a separate file from my own environment settings (zzz_userdefined in ur example) and source it after 66-all up runs
This seems to have done the trick. Though I guess that's due to what @ Eric mentioned regarding the literal interpretation of $PATH. Strange that it suddenly stopped working, but I guess it's stranger that it even worked in the first place.
eric wrote Do you have enabled again the boot-user@ service?
and please like i answered you, show me the output [...]
Like I mentioned earlier, I have used timeshift to restore the backup from before the 66-update. So the output would be already working, since I hadn't changed it at the time of the backup.

I'm quite certain the root of the issue is as described here:
You cannot set your PATH like you do. PATH=$PATH:/rep is a sh/bash/zsh/... thing. I mean the sh interpreter will recognize the $PATH term and change it by the value of the variable. But execl-envfile do not know anything about that and the $PATH will be interpreted as it. So, if you echoing your PATH variable it will be literally PATH=$PATH:/home/magicalsenpai/.local/bin and not PATH=/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/bin:/home/magicalsenpai/.local/bin like you expect.
So I'll reupdate and if everything goes well, set the title to solved.

Thanks everyone

EDIT:
The issue with my keybindings was completely my fault, I had accidentally turned off my super-key.
magicalsenpai wrote This seems to have done the trick. Though I guess that's due to what @ Eric mentioned regarding the literal interpretation of $PATH. Strange that it suddenly stopped working, but I guess it's stranger that it even worked in the first place.
yeah, i use a lot of $ in my env file, thats why indeed just source after 66-all runs and source it after(basically its my .profile/.bash_profile/.zprofile env file)
@ negative
the main disadvantage with this approach is that any service started on your user supervision tree doesn't inherit of the environment variable.

Powered by Obarun