On 5/31/23 19:46, Richard L. Hamilton wrote: > I can e.g. run dtpad from a command, although it takes a long time to start, > since ttdbserverd and/or ttesssion are not running.
Hi Richard I remember resolving a few issues like that by adding the hostname of the machine to /etc/hosts pointing to 127.0.0.1. Have you looked into /var/dt/Xerrors or ~/.dt/errorlog? > * start those while still using the native (lightdm) windown and session > management? Something like that works on my Debian (aarch64) machine: $ cat > /usr/share/xsessions/cde.desktop <<EOF [Desktop Entry] Name=CDE Comment=This session logs you into the Common Desktop Environment Exec=/usr/dt/bin/Xsession TryExec=/usr/dt/bin/Xsession Icon= Type=Application DesktopNames=CDE EOF > * add a session to those CDE knows about I had some success with something like this: $ cat > /usr/dt/config/C/Xresources.d/Xresources.twm <<EOF Dtlogin*altDtName1: Twm Dtlogin*altDtKey1: /usr/bin/twm Dtlogin*altDtStart1: /usr/bin/twm Dtlogin*altDtLogon1: Twm EOF According to the dtlogin man page, you define an Xresources.* file for each session type and append an incrementing number to each of those resource definitions. So if you have another windows manager you would like to use, you define altDtName2, altDtKey2, etc. I haven't yet figured out why there's an altDtKey and an altDtStart resource. But we'll get there... > And what has changed since CDE went open source to the extent that something > might be replaced with something else not natively CDE, or might otherwise be > unfamiliar? We don't like change. :) Cheers, J. _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
