Hello list, I appologize ahead of time if this has already been brought up, but I couldn't find anything about this yet.
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.
Any help would be greatly appreciated.
Thanks, Doug
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
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
Paul Menzel schreef:
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.
You are writing about FreeNX but you mean the open source NX libraries from Nomachine. That's confusing.
FreeNX is a NX-server system, like x2go is. FreeNX is not a part of X2go.
With regards, Paul van der Vlis.
Am Mittwoch, den 27.05.2009, 09:03 +0200 schrieb Paul van der Vlis:
Paul Menzel schreef:
Am Dienstag, den 26.05.2009, 14:04 -0400 schrieb Douglas M. Stanley:
[…]
You are writing about FreeNX but you mean the open source NX libraries from Nomachine. That's confusing.
FreeNX is a NX-server system, like x2go is. FreeNX is not a part of X2go.
Of course. Thanks for the clarification!
Bests,
Paul
Douglas M. Stanley schreef:
Hello list, I appologize ahead of time if this has already been brought up, but I couldn't find anything about this yet.
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.
Any help would be greatly appreciated.
Hello,
I don't have this problem with X2go, but I had it in the past in FreeNX. (I am running FreeNX for many years on many machines with Debian Sarge and Etch).
In FreeNX you can tell what to do when you want to start KDE or Gnome, in my case Gnome. I configured it so that not Gnome was starting directly, but a script, what started Gnome. In that script I did put things like this:
umask 0002 (setting the umask) export TESTVAR=test21 (setting environment) . ~/.gnomerc (running scripts) /usr/bin/X11/setxkbmap -rules xfree86 -model pc104 -layout us -option "" /usr/bin/gnome-session (start gnome)
The setxkbmap option helped against the keyboard problems. Maybe this can help you in finding the problem.
With regards, Paul van der Vlis.
Dear list,
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.
[…]
As written by Heinz [1] this issue was fixed in x2goserver 3.0.0-2.
Today I noticed this problem again on a different system and found out that I had not disabled the check box »Tastaturlayout behalten« under Sitzungsvoreinstellungen → Einstellungen → Tastatur (translation: keep keyboard layout under system settings → settings → keyboard).
The forms are set to de pc105/de and it then works for me although I am using a different keyboard layout (Neo [2]) for one user (under the session x2goclient_gtk is started from and in the started GNOME session which is loading a xmodmap file during start up).
So the wrong keyboard mapping still shows up, if you want to keep the layout. Is this intended? Should there be a warning or explanation next to the check box?
Thanks,
Paul
[1] https://lists.berlios.de/pipermail/x2go-dev/2009-July/000049.html [2] http://neo-layout.org/
-
Brian Moss -
Douglas M. Stanley -
Paul Menzel -
Paul van der Vlis