freenx-team team mailing list archive

[Marcelo Boveto Shima <marceloshima@xxxxxxxxx>]

This happens because Intrepid uses the evdev driver.

The workaround is to configure the keyboard map to evdev, but this will break
the keyboard configuration on hardy/gutsy and windows clients.

-- 
Wierd/Broken keyboard inside NX session behavior on intrepid(client) and hardy(server)
https://bugs.launchpad.net/bugs/290346
You received this bug notification because you are a member of FreeNX
Team, which is the registrant for FreeNX Server.

Status in FreeNX open source NX Server: New

Bug description:
After upgrading to Intrepid, remote session via NX no more react to arrow keys and randomly stops responding to keyboard at all.
Arrows on numeric pad, do work.

Reconnecting from another machine (not intrepid) randomly helps.
No errors or suspicions messages in logs.

Rest of the users of the same freenx instance with Hard/Gutsy as client working fine.

I am using latest nxclient from NoMachine which maybe the problem here.