![]() ![]() In any event, the above _is_ reproducible if any developers want to test. So perhaps it is a combination of Ubuntu and the application. Pressing Shift-ScrlLk(NumLk) returns the keyboard to alpha, but this time _no_ NumLk LED is on. Logout with NumLk turned off on the remote (and the T30) and now I'm back to no LED and no '2' when I press 'k' on the T30. Turn it back on (in the T30) and NumLk control from the remote now works. ![]() NumLk control from the remote now has no effect on the T30 target. Test again: this time I turn off the "Remember NumLock State" in the T30. Pressing Shift-ScrlLk(NumLk) returns the keyboard to alpha, but LED is still on. The T30 is left in a NumLk state this time numbers on the keypad are working (type 'k' and the result is '2'). I leave the NumLk key enabled via the remote NX and logout. ![]() Log back in to the T30 and press NumLk on the remote, NumLk key on the T30 goes on and off properly (I have the two machines side by side so it's easy to monitory). Oddly enough, I log back in via NX to the T30 and then log back out and NumLk is no longer enabled, nor is the NumLk LED on. The only way that I could get the alpha keys back was to do as you suggested Shift-ScrlLk( NumLk), and the LED stays on. Immediately the NumLk LED came on and the numeric keys were enabled. Fresh install of 8.04.1 on an IBM Thinkpad T30, no issues with NumLk.Īnd NX'ed into the T30 to verify all was working. I can verify that this happens with NX server: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |