Hi,
I use x2goclient to connect to a x2goserver, both as installed by gentoo linux. I believe the gentoo versions are "special" in the sense that it uses the NoMachine's version of the nxagent.
Now when I connect and I press AltGr+<, then the result should be the character | but the actual result is < The problem also occurs with the @ character, which is normally obtained by pressing AltGr+@, but in just results q instead of @.
Any ideas? The session settings seem to be OK. It doesn't matter whether I tell x2goclient to keep keyboard settings or whether I explicitly configure de layout.
Server-side is nx-3.5.0.14 (includes nxagent) x2goserver-3.1.1.3
Client-side is net-misc/nx-3.5.0.14 x2goclient-3.99.2.1
Regards, Sven Köhler
Hi Sven,
On Fr 13 Jul 2012 00:54:15 CEST Sven Köhler wrote:
Hi,
I use x2goclient to connect to a x2goserver, both as installed by gentoo linux. I believe the gentoo versions are "special" in the sense that it uses the NoMachine's version of the nxagent.
Now when I connect and I press AltGr+<, then the result should be the character | but the actual result is < The problem also occurs with the @ character, which is normally obtained by pressing AltGr+@, but in just results q instead of @.
Any ideas? The session settings seem to be OK. It doesn't matter whether I tell x2goclient to keep keyboard settings or whether I explicitly configure de layout.
Server-side is nx-3.5.0.14 (includes nxagent) x2goserver-3.1.1.3
Client-side is net-misc/nx-3.5.0.14 x2goclient-3.99.2.1
Regards, Sven Köhler
please send the output of ,,setxkbmap -print" (called from within the
session).
Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 13.07.2012 13:13, schrieb Mike Gabriel:
please send the output of ,,setxkbmap -print" (called from within the session).
That's the output:
$ setxkbmap -print Couldn't interpret _XKB_RULES_NAMES property Use defaults: rules - 'base' model - 'pc105' layout - 'us' xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+us+inet(pc105)" }; xkb_geometry { include "pc(pc105)" }; };
After executing "setxkbmap de" inside the session, the issues goes away and the output is: $ setxkbmap -print xkb_keymap { xkb_keycodes { include "xfree86+aliases(qwertz)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+de+inet(pc105)" }; xkb_geometry { include "pc(pc105)" }; };
Regards, Sven
Am 13.07.2012 23:45, Sven Köhler schrieb:
After executing "setxkbmap de" inside the session, the issues goes away and the output is:
This is a commen problem, that should probably be fixed. We solved it by adding setykbmap to our .x2gosession, which we have as default desktop environment on our thin clients (As well as a "(sleep 10 && metacity --replace &)" to fix the metacity's keyboard bug).
Cheers
Morty
Am 13.07.2012 23:50, schrieb Moritz Strübe:
Am 13.07.2012 23:45, Sven Köhler schrieb:
After executing "setxkbmap de" inside the session, the issues goes away and the output is:
This is a commen problem, that should probably be fixed.
So the problem is known? Is there a patch? You need to know anything more to properly solve the issue?
We solved it by adding setykbmap to our .x2gosession, which we have as default desktop environment on our thin clients (As well as a "(sleep 10 && metacity --replace &)" to fix the metacity's keyboard bug).
So everything I put in ~/.x2gosession is executed before my xfce session is started?
Regards, Sven
Hi,
On Fr 13 Jul 2012 23:50:51 CEST Moritz Strübe wrote:
Am 13.07.2012 23:45, Sven Köhler schrieb:
After executing "setxkbmap de" inside the session, the issues goes away and the output is:
This is a commen problem, that should probably be fixed. We solved it by adding setykbmap to our .x2gosession, which we have as default desktop environment on our thin clients (As well as a "(sleep 10 && metacity --replace &)" to fix the metacity's keyboard bug).
the problem is already solved. Make sure you have
x2goserver >= 3.1.1.3 x2goagent >= 3.5.0.12
Make sure the session profile in x2goclient does not set a custom
keyboard profile.
Then for testing purposes you can call ,,x2gosetkeyboard'' on the
server side after the session has started. After that check
,,setxkbmap -print''. You should see a keyboard configuration that
matches your client-side keyboard configuration (call setxkbmap -print
on the client, as well).
If that works, put ,,auto'' into the session profile field kbtype
(Keyboard field in the session profile GUI). And try to start another
session with the server. The keyboard should now be set. For X2Go
Client a change of the session profile GUI template is still pending.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 14.07.2012 11:26, schrieb Mike Gabriel:
Hi,
On Fr 13 Jul 2012 23:50:51 CEST Moritz Strübe wrote:
Am 13.07.2012 23:45, Sven Köhler schrieb:
After executing "setxkbmap de" inside the session, the issues goes away and the output is:
This is a commen problem, that should probably be fixed. We solved it by adding setykbmap to our .x2gosession, which we have as default desktop environment on our thin clients (As well as a "(sleep 10 && metacity --replace &)" to fix the metacity's keyboard bug).
the problem is already solved. Make sure you have
x2goserver >= 3.1.1.3 x2goagent >= 3.5.0.12
But I have that already and the problem still exists. I have x2goserver-3.1.1.3 nx-3.5.0.14 (includes nxagent)
So unless patches are in x2goagent-3.5.0.12 that didn't make it into nomachine's nx release, then I should have all that's needed.
Make sure the session profile in x2goclient does not set a custom keyboard profile.
It doesn't.
Then for testing purposes you can call ,,x2gosetkeyboard'' on the server side after the session has started. After that check ,,setxkbmap -print''. You should see a keyboard configuration that matches your client-side keyboard configuration (call setxkbmap -print on the client, as well).
Didn't work. x2gosetkeyboard seemed to wait for something to happen for about 10 seconds, and then terminated. Output of setxkbmap -print didn't change and was still not correct.
-
Mike Gabriel -
Moritz Strübe -
Sven Köhler