66-enable -t desktop -S dbus consolekit lightdm
66-enable: fatal: unable to find tree: /home/sno-flah-ke/.66/system/desktop: No such file or directory
This is obviously wrong, when 66 says it is trying to find a tree in /home/user/.... you are running the command as user. DMs want dbus and consolekit running as root because they run as root themselves. The user trees should be made depending on the necessities of the desktop you are running.
https://wiki.obarun.org/doku.php?id=dbus_and_dm
For some desktops it is critical you make the final user 66 step.
I don't use this stuff myself but made an lxdm service (out of the lightdm-66serv
lxdm and followed the steps in the wiki. On reboot it worked. A good test from console is to switch to tty12 and login as user, and see if your % 66-intree -zg user tree is running.
That last step in the wiki requires a deeper understanding of 66. A new tree should be made if none exists. The tree must be "Enabled" and if multiple user trees exist and you don't specify the name of the tree in the 66-enable command, it should also be "c"urrent.
% 66-tree -ncE myUserTree
% 66-enable -S dbus-session@ myusername
If using the -S gives you a failing message, that means that the "root level" tree boot-user is not running yet. Which means a scandir in /run/66/ for the user ID (usually 1000 for the first user in the system) is not active yet. "# 66-all -v2 -t boot-user up " should make it active, or on reboot, if everything was done right, it will be active. As soon as the user logs into the system via console or on DM the user trees are executed and services are supervised for that user.