freenx-team team mailing list archive

[Marcelo Boveto Shima <marceloshima@xxxxxxxxx>]

On Wed, Oct 29, 2008 at 4:05 AM, eugenesan <eugenesan@xxxxxxxxx> wrote:

> You mean Intrepid cannot share X sessions with other OS? That's bad!


No, I mean that you just have some more configuration work.

1 - You need to use the kbd (default on < intrepid) driver for your keyboard
on every client.
      So you need to configure xorg.conf to use kbd on intrepid. This is the
best solution for now,
      it will work like before.

2 - You can use the evdev (default on intrepid) driver on every client. And
configure the
      session on the server to use evdev keymap. But some keys on windows
client will not
      work properly.

What was thinking people that made that decision?


Xorg is starting to support input hotplug. This is the reason to switch to
evdev driver by default.
Evdev supports keyboards, joysticks, mouses and probably touchpad too. So is
is the way to go.

Will there be solution for the problem, maybe future?
>

Yes, I don't know if this can be fixed on freenx alone, but can be fixed on
nx programs.

-- 
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.