I am also having the problem with the Qt client.
Need to read through 1 and 2.
On Tue, May 26, 2009 at 6:33 PM, Paul Menzel < paulepanter@users.sourceforge.net> wrote:
Dear Douglas,
Am Dienstag, den 26.05.2009, 14:04 -0400 schrieb Douglas M. Stanley:
[…]
I recently set up x2go in a xen guest, and when I try to connect to it with the gtk client, the keyboard isn't right. Everything seems to work, except the arrow keys. If I turn numlock on/off, then the arrows on the keypad seem to work, but not the normal arrow keys. I've tried everything I can think of to set the keyboard both on the client and on the actual host. Everything is set to 105key qwerty US, but the arrow keys still don't work.
The maemo client using the directional pad seemed to work fine simulating the arrow keys, so I'm not sure if it would work with the QT client or not as I haven't tried that client yet.
Anyone else run into this issue yet? It may very well be due to the machine running under xen, so I'm not sure if anyone else is doing something similar or not.
I do have the same problem and I believe it is related to FreeNX and not XEN.
Which desktop environment do you use? Have you tried this with other X2go clients? I use x2goclient_gtk and GNOME (on the remote machine). In the beginning I get an error from gnome-settings-daemon 2.24 (it crashed) [1].
The up-arrow is mapped to print and so on. (You can check this with xev.)
This bug with FreeNX is being discussed on [2]. Unfortunately I have not had time to try this out because the fixed gnome-settings-daemon has not entered Debian Sid yet.
Thanks,
Paul
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528499 [2] http://lists.kde.org/?l=freenx-knx&m=123072320912229&w=2
X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev