On 08/12/2012 09:45 PM, Slávek Banko wrote: >> Serious work went into updating tsak after 3.5.13. I don't know all of the >> > patches but there were many. I don't know whether those patches can be >> > backported. Check bug reports 898 and 906 for most of the fixes. >> > >> > Darrell >> > Yes, I recall all the CPU at 100% due to tsak fun... > Darrell, all patches on the SAK I carefully backport to v3.5.13-sru. I believe > that I have not overlooked any SAK patch. I have no clue why UseSAK=true causes the graphical kdm-greeter to fail. It has not been that long ago I was using tsak with the graphical greeter. What is strange is that it began to fail for both R14 and 3513-sru at about the same time 3 weeks or so ago. (it could just be coincidence in timing) If SAK was working and backported, I wouldn't mind using it, but at the same time, it's not one of those things I've ever been too concerned about in a home or small-office setting. If a bad guy has physical access to a box, all you have to do is pop in a boot CD and pull the power-cord. All the great login security in the world won't help in that situation...... I don't know kdm/tdm greeter code well enough to know what would make it fail to load a graphical greeter that easily. But, reading through the full kdmrc, it looks like GrabServer=true may be to blame. That reads: # Hold the X-server grabbed the whole time the greeter is visible. This # may be more secure, but it will disable any background and other # X-clients started from the Setup script. # Default is false #GrabServer=true If the SAK code in 3513-sru has the effect of setting GrabServer=true, then that could explain the graphical chooser failure... -- David C. Rankin, J.D.,P.E.