deloptes composed on 2019-07-24 20:00 (UTC+0200): > Mike Bird wrote: >> FWIW I'm not seeing that with several sysvinit Busters - mostly amd64 >> or multiarch but also at least one very very slow 192MB i386 test box. > It is a known bug - Trinity bug? Systemd? Debian? # grep RETT /etc/os-release PRETTY_NAME="Debian GNU/Linux bullseye/sid" # dpkg -l | grep outh # systemctl list-unit-files | egrep 'outh|tty7' # systemctl list-units | egrep 'outh|tty7' # grep outh /lib/systemd/system/tdm.service Conflicts=getty@... plymouth-quit.service After=systemd-user-sessions.service getty@... plymouth-quit.service # Nothing should ever wait on something that does not exist. > I do not recall which one, but the essence is that in > /lib/systemd/system/tdm.service > you should remove > Conflicts=getty@... plymouth-quit.service > or just comment it out. Then systemd will shutdown tdm properly Instead, I tried two versions of /etc/systemd/system/tdm.service, both of which worked: First try: ********** [Unit] Description=Trinity Display Manager Documentation=man:tdm-trinity(1) Conflicts= After= [Service] # temporary safety check until all DMs are converted to correct # display-manager.service symlink handling ExecStartPre=/bin/sh -c '[ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "tdm" ]' ExecStart=/opt/trinity/bin/tdm Restart=always Second try: *********** [Unit] Conflicts= After= [Service] -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/