On Sat, 21 Dec 2019 22:33:22 +0100 deloptes deloptes@gmail.com wrote:
James D Freels wrote:
It is at this point, where I need some help in how to fix it, and I suspect that all debian/buster users may have the same issue, but not sure of course. I hope I can help get his bug fixed before the final release of TDE for buster.
Thanks again.
Jim Freels, PhD (retired)
I am amazed that no one suggested following:
There is a known bug related to systemd in /lib/systemd/system/tdm.service Just comment out the Conflicts line
$ cat /lib/systemd/system/tdm.service [Unit] Description=Trinity Display Manager Documentation=man:tdm-trinity(1) #Conflicts=getty@tty7.service plymouth-quit.service After=systemd-user-sessions.service getty@tty7.service plymouth-quit.service
[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
This a hacky solution that can theoretically led to problems (afaik depending on video drivers used plymouth could prevent Xorg from starting). The source of the problem here is that tdm doesn't correctly signal to plymouth to quit. So correct action is to disable/uninstall plymouth, not to edit tdm.service