Hey all,
Recently, TSAK has started messing up my system. Whenever I hit the caps lock key, the keyboard basically freezes. The CPU does not thrash, but I am almost certain it is tsak. Basically it would not allow me to type in any new letters, and the caps light gets locked, I then have to reboot to correct it ( well i probably could have killed tsak)
Is TSAK grabbing ther wrong keys? this is an lenovo x220. here is my xev output with tsak disabled:
KeymapNotify event, serial 21, synthetic NO, window 0x0, keys: 0 0 0 0 16 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 30, synthetic NO, window 0x1200001, root 0xb2, subw 0x0, time 431876, (-866,348), root:(100,371), state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES, " XLookupString gives 1 bytes: (0d) " XFilterEvent returns: False
PropertyNotify event, serial 33, synthetic NO, window 0x1200001, atom 0x1c3 (_NET_WM_ICON_GEOMETRY), time 431952, state PropertyNewValue
KeyPress event, serial 34, synthetic NO, window 0x1200001, root 0xb2, subw 0x0, time 432888, (-866,348), root:(100,371), state 0x0, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x1200001, root 0xb2, subw 0x0, time 432968, (-866,348), root:(100,371), state 0x2, keycode 66 (keysym 0xffe5, Caps_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
ClientMessage event, serial 34, synthetic YES, window 0x1200001, message_type 0x17c (WM_PROTOCOLS), format 32, message 0x17b (WM_DELETE_WINDOW)
Calvin
On Wednesday 07 of March 2012 00:27:08 Calvin Morrison wrote:
Recently, TSAK has started messing up my system. Whenever I hit the caps lock key, the keyboard basically freezes.
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.
Slávek --
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 (startx) 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
On Wednesday 07 of March 2012 02:14:18 Darrell Anderson wrote:
Tim,
Is tsak enabled when starting the X session from the command line (startx) 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
I use KDM in which case the "saboteur" tsak is running.
Slávek --
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 (startx) 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
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@pearsoncomputing.net wrote:
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
(startx)
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@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@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
Is tsak enabled when starting the X session from the
command line (startx)
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
keyboards and I don't see these issues. I could test more through TDM....
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.
Ok, thanks. I think SAK is a sound idea, but as I typically run X from the command line, I have little experience with TDM. Occasionally I test TDM, but not as often I should.
Why is SAK needed for graphical logins but not command line logins?
Darrell