7 Mar
2012
7 Mar
'12
4:06 a.m.
Just in general,
New features always miss unhandled errors or exceptions or oddball
scenarios - tsak isn't bad there are just some things to work out. That's
how I see it! :)
On Mar 6, 2012 9:27 PM, "Timothy Pearson" <kb9vqf(a)pearsoncomputing.net>
wrote:
(startx)
As I said earlier - I have observed the exact same
behavior
== dead keyboard -
in response to the Num Lock. When I connect a USB keyboard
to the other, so
that it works correctly.
I must admit that I am very angry to SAK. I see no benefit
in it, but I see
the annoying bugs that brought. Therefore, I always feels
like the best
solution UseSAK set to false. I do not see anything that I
lost - but to get
rid of the unnecessary SAK and errors associated with it.
Tim,
Is tsak enabled when starting the X session from the command line or only through TDM? If yes, then how is tsak
enabled when X is started
through startx? If no, then does tsak serve a purpose for startx users?
Just asking because I am a startx person and I use PS/2 kyeboards and I
don't see these issues. I could test more through TDM....
Darrell
Only from TDM. tsak brings significant security benefits, but apparently
contains several bugs. I suggest turning it off if you are experiencing
problems and know that no one else has access to your computer via a
second graphics-capable account.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting