This fixed the problem.� I think I recall plymouth is needed for kde>3.5 ?

Also, I tried the faster DefaultTimeout times, and that was not the 
issue here.

Still not sure if this is a bug, but it certainly appears that if 
plymouth is in the system, it will cause tdm to behave like this ?

On 12/21/19 12:46 PM, Dr. Nikolaus Klepp wrote:
> You can saferly purge all plymouth* packages. It's just eyecandy and a source of interestring problems.
>
> Nik