usr99

I also have that problem If I select anything except localhost:0home in dtlogin, it will not load a session file and become unusable. I must restart the system (gentoo x64) , dtsession is broken. I remember it working perfectly with slackware or freebsd when it was 2.3.* with older Xorg versions.

I also have that problem If I select anything except localhost:0home in dtlogin, it will not load a session file and become unusable. I must restart the system (gentoo x64). I remember it working perfectly with slackware or freebsd when it was 2.3.* with older Xorg versions.

I also have that problem If I select anything except localhost:0home in dtlogin, it will not load a session file and become unusable. I must restart the system (gentoo x64). I remember it working perfectly with slackware or freebsd when it was 2.3.*

I also have that problem If I select anything except localhost:0home in dtlogin, it will not load a session file and become unusable. I must restart the system (gentoo x64)

deleted

I'm not a developer, but I belive I found the cause, dtlogin must be started from xorg/xserver or the distro init, instead of manually starting it from console, as X manages "display" and other variables being passed to CDE to function properly. Home/Current sessions would be kept and function properly so, but only for root. For ArchLinux or other distros like Gentoo it would be the same, set the configs to launch a login manager after boot, from X and not other scripts

I'm not a developer, but I belive I found the cause, dtlogin must be started from xorg/xserver or the distro init, instead of manually starting it from console, as X manages "display" and other variables being passed to CDE to function properly. Home/Current sessions would be kept and function properly so, but only for root. For ArchLinux or other distros like Gentoo it would be the same, set the configs to launch a login manager after boot, from X and not init or other scripts

I'm not a developer, but I belive I found the cause, dtlogin must be started from xorg/xserver or the distro init, instead of manually starting it from console, as X manages "display" and other variables being passed to CDE to function properly. There are some hanlder scripts which don't get the variables, if CDE is slow it's why. Home/Current sessions would be kept and function properly so. For ArchLinux or other distros like Gentoo it would be the same, set the configs to launch a login manager...