I don't know if it is a TDM bug or not.� I DO know that if I boot with lightdm or lxdm and NOT tdm, then this problem does not occur. My guess is that perhaps tdm is starting at a different "level" then lxdm or lightdm, and causes a conflict of some kind with something else? On 12/21/19 3:02 AM, Nick Koretsky wrote: > I dont think its a bug in TDE, this looks like some systemd problem, so a > steps to deal with systemd problems has to be followed. > Starting with 'systemd-analyze blame' and 'systemd-analyze critical-chain'.