Keyboard Arrow key misbehavior

[CollaboratorGCM]

I cannot pin-point it, the problem emerges from FirstRUN processing. I have noticed that arror keys behave as expected BEFORE I click OK in FirstRUN. But problem is created after Firstrun changes made.

Typically I change keyboard, numlock, timezone, internet time, and hostname on FirstRUN for Slackos. FirstRUN reports a hostname change and offers to restart Xwindows, which I allow. Recent Slackos V7 and V8 causes the arror keys to behave inappropriately when the desktop re-emerges.

I also found that re-entering FirstRUN and resetting or re-making new changes will NOT affect the arror keys after initial FirstRUN.

Then, I just discover that the resetting effort mentioned in the prior paragraph MUST be accompanied by a desktop restart to get the proper arrow key behavior to return.

I have NOT pin-pointed which of the fields contributes to the culprit, ... yet.

[01micko]

Might have to have a look at the keyboard layout routine in quicksetup

[CollaboratorGCM]

It seems the problem surfaces after FirstRUN no matter if changes are made or not. It is NOT present upon on desktop before hitting the OK button in FirstRUN.

The problem will disappear after a desktop restart; I used Ctrl-Alt-Backspace to restart, then "xwin" in console. Upon arrival on desktop, the problem is gone.

[CollaboratorGCM]

Spoke too soon; Rerunning Firstrun from Menu>Setup>...FirstRUN and completing the normal changes I traditionally make, I hit the OK key only to find that moments later after time change from the internet the problem is back.

So, it appears to be FirstRUN related with/without user changes.