Date: Tue, 28 Nov 2023 13:49:12 -0800 From: Cy Schubert <Cy.Schubert@cschubert.com> To: "Rolf M. Dietze" <rmd@orbit.in-berlin.de> Cc: freebsd-current@freebsd.org Subject: Re: CDE on FreeBSD 14.0 Release Message-ID: <20231128214912.D7116147@slippy.cwsent.com> In-Reply-To: <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de> References: <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20231127172506.Horde.iiBmVTtnl5OM_J0h4cvdd7M@webmail.in-berlin.d e>, "Rolf M. Dietze" writes: > Hi, > > might be that I am on the wrong list for this, since my Problem > exists on 14.0Release. > > After an out of the box install of FreeBSD 14.0 Release and following > https://forums.freebsd.org/threads/setting-up-common-desktop-environment-for- > modern-use.69475/ First, unless you plan on using the CDE calendar, you don't needs the dtspc entry in inetd.conf. I'm currently running CDE, installed using pkg, on 14.0-RELEASE using dtlogin at $JOB. At home I use CDE on 15-CURRENT. I use xdm at home instead because dtlogin doesn't support PAM* but xdm does. Caveat, if you use xdm you will need to add dtsession to your .xsession file. * My home network uses MIT KRB5 to serve passwords and LDAP to serve UID/GID information. This requires pam_krb5, and as dtlogin is not PAM aware it can only work with accounts in /etc/passwd. Hence xdm. I'll probably submit a pull request to the CDE development team one day but considering all the other things on my plate, PAM support within dtlogin is pretty low on my priority list. > I am stuck with CDE. CDE loads, dtlogin starts an presents the login > or greeter window, but upon logging in I get a popup telling > "The desktop messaging system could not be started". Guess I am > missing some config steps. Any pointer for further reading? > I had CDE running on 13.2Release Make sure your /etc/hosts has an entry for localhost. Also make sure your machine's PTR record is correct and that it matches its A record. It's most likely your hostname doesn't match any IP on your network. Just add your correct hostname's IP to /etc/hosts or if using dhcp, prefix your hostname to the localhost entry in /etc/hosts like this, 127.0.0.1 my_hostname_whatever_it_is localhost localhost.my.domain Also make sure rpcbind is running. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org NTP: <cy@nwtime.org> Web: https://nwtime.org e^(i*pi)+1=0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20231128214912.D7116147>