Activity for usr99
-
usr99 modified a comment on ticket #155
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...
-
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...
-
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. @Lusvit For ArchLinux or other distros like Gentoo it would be the same, set the configs to launch a login...
-
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...
-
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.
-
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
-
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
-
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. there are some hanlder scripts which don't get the variables, if CDE is slow it's why
-
I'm not a developer, but I belive I found the cause, the dtlogin exec 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. there are some hanlder scripts which don't get the variables, if CDE is slow it's why
-
I'm not a developer, but I belive I found the cause, the dtlogin exec 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
-
that fixed it
-
I also have that problem If I select anything except localhost:0home in dtlogin, it will not load a session file and I must restart the system (gentoo x64)
-
that fixed it, but it doesn't create a dt session file in home, and at every login it defaults to the first login screen with th manual window and default theme
-
I've managed to compile cde 2.5.1 source on gentoo amd64 (nonmultilib), dtlogin and dtwm starts but I'm promted with the window: action required - the desktop messaging bus could not be started - 1, 2, 3 OK] I've installed most dependencies if i dismiss the window it says tooltalk is not running
-
I've managed to compile cde 2.5.1 on gentoo amd64 (nonmultilib), dtlogin and dtwm starts but I'm promted with the window: action required - the desktop messaging bus could not be started - 1, 2, 3 OK] I've installed most dependencies if i dismiss the window it says tooltalk is not running
-
I've managed to compile cde 2.5.1 on gentoo, dtlogin and dtwm starts but I'm promted with the window: action required - the desktop messaging bus could not be started - 1, 2, 3 OK] I've installed most dependencies if i dismiss the window it says tooltalk is not running
1