# tail of journal Sep 23 23:27:51 systemd[1]: Starting User Login Management... Sep 23 23:27:51 systemd-logind[2198]: Failed to connect to system bus: No such file or directory Sep 23 23:27:51 systemd-logind[2198]: Failed to fully start up daemon: No such file or directory Sep 23 23:27:51 systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Sep 23 23:27:51 systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Sep 23 23:27:51 systemd[1]: Failed to start User Login Management. Sep 23 23:27:51 systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5. Sep 23 23:27:51 systemd[1]: dbus.socket: Start request repeated too quickly. Sep 23 23:27:51 systemd[1]: dbus.socket: Failed with result 'start-limit-hit'. Sep 23 23:27:51 systemd[1]: Failed to listen on D-Bus System Message Bus Socket. Sep 23 23:27:51 systemd[1]: Starting Load Kernel Module drm... Sep 23 23:27:51 systemd[1]: modprobe(a)drm.service: Deactivated successfully. Sep 23 23:27:51 systemd[1]: Finished Load Kernel Module drm. Sep 23 23:27:51 systemd[1]: systemd-logind.service: Start request repeated too quickly. Sep 23 23:27:51 systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Sep 23 23:27:51 systemd[1]: Failed to start User Login Management. Sep 23 23:27:51 systemd[1]: display-manager.service: Found left-over process 1166 (tdecryptocardwa) in control group while starting unit. Ignoring. Sep 23 23:27:51 systemd[1]: display-manager.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 23 23:27:51 systemd[1]: display-manager.service: Found left-over process 1175 (dcopserver) in control group while starting unit. Ignoring. Sep 23 23:27:51 systemd[1]: display-manager.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 23 23:27:51 systemd[1]: display-manager.service: Found left-over process 2090 (dcopserver) in control group while starting unit. Ignoring. Sep 23 23:27:51 systemd[1]: display-manager.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 23 23:27:51 systemd[1]: Starting X Display Manager... Sep 23 23:27:51 display-manager[2208]: /etc/vconsole.conf available Sep 23 23:27:51 display-manager[2208]: KEYMAP: us Sep 23 23:27:51 display-manager[2208]: Command: localectl set-keymap us Sep 23 23:27:51 display-manager[2208]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Sep 23 23:27:51 localectl[2215]: Failed to connect to bus: No such file or directory Sep 23 23:27:51 display-manager[2204]: Starting service tdm Sep 23 23:27:51 systemd[1]: Started X Display Manager. Sep 23 23:28:13 tdm[2232]: pam_systemd(xdm:session): Failed to connect to system bus: No such file or directory Sep 23 23:28:13 tdm[2232]: pam_unix(xdm:session): session opened for user root(uid=0) by root(uid=0) Sep 23 23:28:13 tdm[2232]: pam_unix(xdm:session): session closed for user root Sep 23 23:29:32 systemd[1]: Starting Cleanup of Temporary Directories... Sep 23 23:29:32 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Sep 23 23:29:32 systemd[1]: Finished Cleanup of Temporary Directories. Sep 23 23:29:32 systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Sep 23 23:30:13 tdm[2346]: pam_systemd(xdm:session): Failed to connect to system bus: No such file or directory Sep 23 23:30:13 tdm[2346]: pam_unix(xdm:session): session opened for user root(uid=0) by root(uid=0) Sep 23 23:30:13 tdm[2346]: pam_unix(xdm:session): session closed for user root # rpm -qa | grep pam | sort pam-1.6.1-4.1.x86_64 pam-config-2.11+git.20240911-1.1.x86_64 pam-extra-1.6.1-4.1.x86_64 pam-manpages-1.6.1-4.1.noarch pam_pwquality-1.4.5-2.3.x86_64 yast2-pam-5.0.0-1.4.noarch # TDM works fine, except if I want to start a login session from it. This is a freshly resurrected SSD in a PC whose motherboard died in August two years ago. I stumbled onto a free motherboard replacement suited to the RAM, CPU, cooler, etc. and got it going today. I managed to upgrade TW from 20220807 to 20240922 without any significant obstacles, until trying to login to any of Plasma, TDE, or IceWM from TDM. Failsafe does start a session with an Xterm, from which starttde opens a normally functioning TDE desktop. Any ideas or suggestions whether this could be a TW problem or a TDM problem, or how to fix it? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ____________________________________________________ tde-users mailing list -- users(a)trinitydesktop.org To unsubscribe send an email to users-leave(a)trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…

Sep 23 23:27:51 systemd-logind[2198]: Failed to connect to system bus: No such file or directory Sep 23 23:27:51 systemd[1]: Failed to listen on D-Bus System Message Bus Socket. Sep 23 23:27:51 localectl[2215]: Failed to connect to bus: No such file or directory Sep 23 23:28:13 tdm[2232]: pam_systemd(xdm:session): Failed to connect to system bus: No such file or directory Sep 23 23:30:13 tdm[2346]: pam_systemd(xdm:session): Failed to connect to system bus: No such file or directory

Any ideas or suggestions whether this could be a TW problem or a TDM problem, or how to fix it?