is one supposed to run dbus-launch command on each startup ?
i.e i have a notification-daemon named Dunst that gives me the error message 'CRITICAL: Cannot connect to Dbus.' when i try to launch it. dbus-dependent software like Dunst can only be started after executing dbus-launch command, and that works with or without my dbus-session@ service file enabled. This makes me think that the dbus-session@ service is redundant.
My non-root tree: 
 ~ 66-intree
Name        : myuser
Initialized : yes
Enabled     : yes
Current     : yes
Contents    : dbus-session@ myuser-log  dbus-session@ myser
I did try the JWM desktop installed from the obarun-installer. Dunst succesfully started without typing the dbus-launch command.
sounds similar to this https://forum.obarun.org/viewtopic.php?pid=3860# p3860 although i wasn't able to get into X ..
so maybe not..
i don't use a session/login manager/DM thingy (i use dunst and it works fine)
my ~/.xinitrc starts openbox with: 
(dbus-launch --sh-syntax --exit-with-session openbox-session)
mind you, i also have this: 
dunstify "not you again :( " &
before that ... i think that launches the daemon .. i can't see where i specifically launch it elsewhere...
but i don't use any user level services either.. 
Name        : root1
Initialized : yes
Enabled     : yes
Current     : yes
Contents    : dhcpcd-log  tty2  dbus-log  dbus  dhcpcd  tty1
probly just ignore me... ")
@ batchee

Starts the dbus-session doesn't mean that the environment variables like DBUS_SESSION_BUS_ADDRESS is available for all processes on your current desktop.
That's exactly does the boot-user@ -66mod module. It will ensure that environment variables are correctly set when you start your user's scandir.
To do so , follow this: https://wiki.obarun.org/doku.php?id=dbus_and_dm

If you have any futher question/trouble, please don't hesitate to ask.
thanks eric
i read the wiki before doing a minimal install.
i looked into my .zsh history and these are all the commands i've typed as root user that relates to 66, dbus and dms: 
pacman --noconfirm -S lightdm-66serv && pacman --noconfirm -S dbus-66serv consolekit2 consolekit-66serv
pacman --noconfirm -S boot-user@ -66mod
66-mods.sh boot-user@ myuser
66-tree -nE myuser-session
66-enable -t myuser-session All-myuser
66-tree -ncE desktop
66-enable -t desktop dbus consolekit lightdm

sudo -u myuser 66-tree -nE myuser
sudo -u myuser 66-enable -t myuser dbus-session@ myuser
other noteworthy stuff.
inside /home/myuser/.66/conf/boot-user/boot-user@ myuser.conf file i do see a line: 
 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/dbus.
/run/user/1001/dbus socket/file does exist
Running services with name dbus: 
PID  USER   Command
834  root   s6-supervise desktop-dbus-log
835  root   s6-supervise desktop-dbus
862  s6log  s6-log -d3 n3 T s1000000 /var/log/66/dbus
867  dbus   dbus-daemon --system --print-pid=4 --nofork --nopidfile --address=unix:path=/run/dbus/system_bus_socket
1066 myuser s6-supervise myuser-dbus-session@ myuser
1069 myuser s6-supervise myuser-dbus-session@ myuser-log
1084 myuser s6-log -d3 n3 T s1000000 /home/myuser/.66/log/dbus-session@ myuser
1088 myuser dbus-daemon --session --print-pid=4 --nofork --nopidfile --address=unix:path=/run/user/1001/dbus
@ batchee
Good for you? you don't ask nothing, i guess it works now ?
@ eric
it did not work by the time i wrote my last message but i did find a solution for my problem.
even though my .xprofile was read at startup, it could not launch dbus related programs.
i use sxhkd hotkey daemon where i start all my programs. Programs and terminals launched by sxhkd that is launched by my .xprofile could never do anything with dbus.
so i made the .xsession file start sxhkd, dunst etc, and now sxhkd could start dbus related programs and launch terminals that could launch dbus related programs as well.
Your configuration for your user tree and dbus-session@ service seem correct.

Have tried to create a frontend service file for your sxhkd daemon?
7 months later
I hope it is ok to resurrect an old thread.

I have issue with s6-supervise desktop-dbus not starting. So I have to start every dbus dependent app with "dbus-launch app" or edit the files in usr/share/xsessions to start the window managers with dbus-launch. Any tips to troubleshoot?
I hope it is ok to resurrect an old thread.
Not really. Could you plz open a new thread for your issue. Thx

Powered by Obarun