Hi,
I have some problem with user tree, maybe I haven' t found the right commands from the documentation...

So I have root trees enabled and working,
sudo 66-intree -zg

Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(548,Enabled,classic) tty@ 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
               ├─(598,Enabled,longrun) udevd-log
               ├─(761,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
               ├─(1097,Enabled,longrun) tty-rc@ tty1
               ├─(1096,Enabled,longrun) tty-rc@ tty3
               ├─(1101,Enabled,longrun) tty-rc@ tty4
               ├─(1099,Enabled,longrun) tty-rc@ tty2
               └─(up,Enabled,module) boot@ system

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(953,Enabled,classic) dhcpcd-log
               └─(954,Enabled,classic) dhcpcd

Name         : users-session
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) setenv@ joe
               ├─(1028,Enabled,longrun) svscan@ joe-log
               ├─(1079,Enabled,longrun) svscan@ joe
               ├─(up,Enabled,module) scandir@ joe
               ├─(up,Enabled,oneshot) mount-run@ joe
               ├─(up,Enabled,module) boot-user@ joe
               ├─(up,Enabled,oneshot) setenv@ gspe
               ├─(1029,Enabled,longrun) svscan@ gspe-log
               ├─(1083,Enabled,longrun) svscan@ gspe
               ├─(up,Enabled,module) scandir@ gspe
               ├─(up,Enabled,oneshot) mount-run@ gspe
               ├─(up,Enabled,module) boot-user@ gspe
               ├─(1035,Enabled,longrun) dbus-log
               ├─(1032,Enabled,longrun) lxdm-log
               ├─(1049,Enabled,longrun) dbus
               └─(1072,Enabled,longrun) lxdm
system boots and I'm able to login and use dm and wm.

Now I want to use some user tree, I've done these steps:
66-intree -zg
66-intree: info: no tree exist yet

66-tree -nE base
66-tree: info: Created successfully tree: base
66-tree: info: Enabled successfully tree: base

66-enable -t base dbus-session@ gspe
66-enable: info: Enabled successfully: dbus-session@ gspe

66-enable -t base xdg-user-dirs
66-enable: info: Enabled successfully: xdg-user-dirs
After logout and reboot, login and my user tree is not initialized
66-intree -zg
Name         : base
Initialized  : no
Enabled      : yes
Starts after : None
Current      : no
Allowed      : gspe
Symlinks     : svc->source db->backup
Contents     : /
               ├─(unitialized,Enabled,oneshot) xdg-user-dirs
               ├─(0,Enabled,longrun) dbus-session@ gspe-log
               └─(0,Enabled,longrun) dbus-session@ gspe
what the contain of your ~/.xession file?
should be something like this: 
# !/usr/bin/bash
_user=obarun
list=( $(ls -1 /home/${_user}/.66/conf/svscan@ ${_user}) )
for i in ${list[@ ]};do
    var=$(</home/${_user}/.66/conf/svscan@ ${_user}/${i})
    for j in ${var[@ ]}; do
		export ${j}
    done
done

66-all up
obviously replace _user=obarun by the good one for you
My .xsession is:
# !/bin/sh

#
# ~/.xsession
#
# Executed by xdm/gdm/kdm at login
#

/bin/bash --login -i ~/.xinitrc
This file should not be created by boot-user@ module?

Even in a fresh install of obarun if I create a new user and enable boot-user@ module .xsession is not present.
This file should not be created by boot-user@ module?
Hum, misdesign. It will create it uniquely if you use the DISPLAY_MANAGER variable which is not a good idea. It should be created even if this variable is not used.

Thanks for the reports.
I've created ~/.xsession manually and it works with new user in obarun.

But I have some problem with void with the exactly same file:
- with lxdm I'm able to login but user tree is not initialized
- with sddm I'm not able to login
- with startx user tree is initialized

I don't undestand why it doesn't works, do you have any suggestion?
gspe wroteI've created ~/.xsession manually and it works with new user in obarun.

But I have some problem with void with the exactly same file:
- with lxdm I'm able to login but user tree is not initialized
- with sddm I'm not able to login
- with startx user tree is initialized

I don't undestand why it doesn't works, do you have any suggestion?
When I started experimenting with 66, the natural way to start was using frontend service files from obarun. But I had a problem. These frontend files were very well tested but they were made for a different distribution with a different set of policies and expectations. Many of them worked perfectly fine for voidlinux, but as I progressed I hit the first snag.
What should I do about the display manager and dbus? voidlinux starts the system bus as root and the display manager autostarts the user bus. obarun devs do not want anything autostarted - which is a valid option. I choose to follow the voidlinux policies and I continue to do so in void-66-services.
66 is very powerfull and flexible. But unfortunately I cannot support the way obarun is configuring the user session. I believe it is in many ways superior to the traditional one from which is a drastic departure.
mobinmob wrotevoidlinux starts the system bus as root and the display manager autostarts the user bus.
Is this dbus-x11 which I think starts with X despite of whether using a DM or not, it was starting on my voids with xinit which by using /etc/X11/Xwrapper allows X to start as user. My solution was to force remove dbus-x11 and everything was OK. Ok means that any DT application that is locked to having user-dbus running spits out errors but keeps working fine till you get to that one and only instance where dbus was necessary for some function. Probably to communicate to cups something needs to be printed.

Policy or not, I believe linux's nature is to allow a certain amount of hacking to customize what you want. Some distros that focus on providing a ready made frozen meal in a window platter have strict policies, and some are "slacker" on policy. I'd like to think of void as below average restrictive. Still, arch is fun.

PS But I do understand that a distro doesn't have to support anyone's hacking
Hi everybody,
thanks for your help.

I've done some more test fist of all I've deleted user tree and tried disfferent configuration.
My conclusion is that is not a 66 problem but a problem is about how DM interacts with ~/.xsession file.
Let me explain better, I've tested sddm and lxdm.

LXDM simply ignores ~/.xsession file, to test this create a .xsession like this: 
# !/bin/bash

export TEST=test
after a login print all your environment variable with printenv and the TEST variable is not there!

SDDM crash if in the .xsession file is present a List of Strings, to test this create a .xsession like this: 
# !/bin/bash

# Declare a string array
LanguageArray=("PHP"  "Java"  "C# "  "C++"  "VB.Net"  "Python"  "Perl")
now you are not able to login with sddm!

This happens in void I don't know why sddm in obarun works.
@ fungal_net : I am not going to propose something that will break the way the system works for others. Anyone is free of course to experiment and hack on their installations.

@ gspe: obarun and void are different distributions, do not expect thing to work exactly the same way.
I've found the root of the problem!
The problem is caused by a combination of using fish shell as user shell and dash shell as system shell and using sddm as DM, I've posted an issue on sddm github page https://github.com/sddm/sddm/issues/1344

So if user use sddm, the solution is to change user user shell to something different of fish shell.

After changing my user shell 66 user tree works perfectly :-) 
66-intree -zg
Name         : base
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : no
Allowed      : joe
Symlinks     : svc->source db->source
Contents     : /
               ├─(1378,Enabled,longrun) dbus-session@ joe-log
               ├─(1382,Enabled,longrun) dbus-session@ joe
               └─(up,Enabled,oneshot) xdg-user-dirs

Powered by Obarun