Sorry for getting backing earlier.
Also, I misspoke originally in the title, it's not an issue with the tree itself (I believe).
fungal_net wroteMaybe move it to a user tree that is not set as Enabled and use .zlogin 66-all -t treename up to start the service after the path has been exported.
But isn't this mostly already done in ~/.xinitrc?
See here:
# !/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
export $(dbus-launch)
/home/magicalsenpai/.config/feh/fehbg &
${cmd} dwm
All services are brought up after the path is set in the 2nd for loop.
Regardless, I manually tried the suggestion.
First I disabled the dwmblocks service
$ 66-disable -t graphics -S dwmblocks
Created a new tree without enabling it
$ 66-tree -n dwmblocks_test
And enabled the dwmblocks service in the tree
$ 66-enable -t dwmblocks_test -S dwmblocks
$ 66-all -t dwmblocks_test up # only ran this to be sure
But it still seems unable to start.
Your other reply about creating a oneshot program did get me thinking though. Perhaps part of the issue is the service starting before X is started. So I'm making a oneshot service at the moment to start dwm and replace the last parts of the .xinitrc file, setting the dwm oneshot service as a dependency of the dwmblocks service could help it work.