Appart from fungalnet informations i will add some intructions to properly deal with user tree and DM and corrects a thing about sddm and consolekit relationship
The task can be tedious to have a dbus envrionment set correctly for a desktop machine, but by chance we have the necessary tools to accomplish this on automatic way.
Follow this:(as fungalnet said you every command beginning by # mean root execution, and $ mean normal user execution)
Assumptions:
- you are on v0.2.x.x 66 package version and testing repo are activated
- you have dbus-66serv and sddm-66serv packages installed on your system
- you have dbus, sddm, consolekit packages installed on your system
- you have dbus, sddm enabled on some root's tree. Now the precision about sddm and consolekit. When you use sddm service do not enable consolekit. Both can enter in conflict. Just let sddm starts consolekit when sddm need it.
1) first at all install boot-user-@ -66mod modules
# pacman -S boot-user-@ -66mod
2) create a new tree with a desire name (e.g boot-user). this is optionnal. The modules can be enabled on every tree. Otherwise it can be a good idea to separate things when you are not accustomed with 66.
# 66-tree -nE boot-user
3) configure the modules to deal with the correct user (e.g oblive)
# 66-mods.sh boot-user-@ oblive
4) enable the modules onto the boot-user tree
# 66-enable -t boot-user boot-user-oblive
Ok, now what do the modules. When you start the machine after the boot procedure the boot-user tree will be launched. This tree will start a scandir for the oblive user with good envrionment into it like the definition of DBUS_SESSION_BUS_ADDRESS XDG_RUNTIME_DIR and so on. Creation of the /run/user/<uid> directory, and so on. Some of those operation need to be made as root (like the run/user directory), that's why the modules is set with root user.
Note: if you have x user you can make the exact same procedure as above replacing oblive by the name of another user. In this case each user will have his own directory with correction permissions on it... yeah multi-session is possible with 66 and multi-seat too.
Anyway, we will now configure the user itself.
5) create a tree named e.g graphics
$ 66-tree -Ecn graphics
6) enable dbus into it and every service that you want but dbus is mandatory
$ 66-enable dbus-session-@ oblive xdg-user-dirs
you're are done.
A tree user tree (and every 66 command is general) react as exactly the same way as root user. So, you deal with service for user as you make it with root.
If you have any question, don't hesitate.
Note: if you want some precision about what do the modules :
$ 66-mods.sh -H boot-user-@
will display the help of the modules boot-user-@