On Thu, Jan 22, 2009 at 12:00 PM, mabawsa wrote:
> Nope on evdev managed keyboards server-side cause all navigation keys to
> map incorrectly.
This is the way it works. With this updated nxagent, it converts the evdev
keycodes into pc105 keycodes. So it is a predictable behavior.
>
> kb101-us
By the navigation keys I mean:
up (mapped to enter), left (nothing), down (nothing), right (nothing)
arrow keys
pageup (nothing), pagedn (nothing), Home (nothing), End (nothing)
Delete (prntscrn), Insert (nothing), prntscrn (nothing)
The brackets show what I have seen when I use evdev managed key
Nope on evdev managed keyboards server-side cause all navigation keys to
map incorrectly.
kb101-us on server and evdev-us on the client causes the delete key to
be mapped as printscrn
For now as long as the client and server are kb101-us the fix works.
I have not tried the jp106 keyboard yet. I w
So, you have this problem with the jp106 keymap?
Did you tried to set the keymap to jp106 on the server too?
There are other keys wrong mapped or just the delete key?
On Thu, Jan 22, 2009 at 2:50 AM, mabawsa wrote:
> Correction:
> The generic 101 US works when it is set on both client and serv
What is your client keymap?
On Wed, Jan 21, 2009 at 8:43 PM, mabawsa wrote:
> Same story using an intrepid client and Hardy server. The navigation
> keys are restored using the generic 101 keyboard but the delete key
> always maps to printscreen. This configuration worked without any fix
> prior
It is not fixed yet. No easy fix, only workarounds.
On Tue, Nov 4, 2008 at 4:26 PM, jmcantrell <[EMAIL PROTECTED]> wrote:
> I noticed that there were some updates to some of the affected packages.
> Can anyone confirm that this is fixed? I have downgraded my client to
> Hardy, so I'm unable to te
