<div dir='auto'><div>Ok, I tried adding options like " -keyboard clone", " -keyboard query" and "keyboard pc105/us,ru,kz", " -keyboard rmlvo/evdev", " -keyboard rmlvo/xfree86" on server in x2goagent.options.. No difference at all. Client has disabled keyboard detection.</div><div dir="auto"><br></div><div dir="auto">Like it's not working. I almost thought it needs reboot or something, but if I write something wrong into x2goagent.options I can't log in right away which implies x2goagent initialized each time I try to login.<br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">10 сент. 2019 г. 15:10 пользователь Ulrich Sibiller <uli42@gmx.de> написал:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">On Tue, Sep 10, 2019 at 10:46 AM <gleb.shipitsyn@gmx.com> wrote:
<br>
>
<br>
> As much as I can see it makes absolutely no difference if x2goclient has switch set on auto-detect keyboard settings and on disabled keyboard detection. Same wrong keycodes.
<br>
>
<br>
> If I force russian keyboard in x2goclient it behaves differently: Shift+2 returns "!", not "@" for example. Comma and dot works properly while slash is not. Kinda weird.
<br>
>
<br>
> Unfortunately I cannot force three keyboard layouts simultaneously and check this way since it does not accept multiple values as argument.
<br>
<br>
Ok, you can disable keyboard detection in x2goclient _and_ force the
<br>
keyboard in /etc/x2go/x2goagent.options:
<br>
<br>
X2GO_NXAGENT_DEFAULT_OPTIONS+=" -keyboard <your choice>"
<br>
<br>
man nxagent shows you the available options:
<br>
<br>
keyboard=<string> or kbtype=<string>
<br>
<br>
query|clone|<model>/<layout>|rmlvo/<rules>#<model>#<lay-
<br>
out>#<variant>#<options>
<br>
<br>
query use the default XKB keyboard layout (see below) and
<br>
only allow clients to query the settings but prevent
<br>
any changes. query is especially helpful for setups
<br>
where you need to set/modify the actual keyboard layout
<br>
using core X protocol functions (e.g. via xmodmap). It
<br>
is used for MacOS X clients to handle some keyboard
<br>
problems that are special for this platform. Note that
<br>
in this case XKEYBOARD will always report the default
<br>
layout which will most likely not match the experienced
<br>
settings.
<br>
<br>
clone ask the real X server for the keyboard settings using
<br>
XKEYBOARD protocol functions and clone them. This is
<br>
the recommended setting. For compatibility reasons it
<br>
is not the default.
<br>
<br>
<model>/<layout>
<br>
use the given model and layout. A value of null/null is
<br>
equivalent to clone. You can not modify keyboard rules,
<br>
variant or options this way. Instead preset values are
<br>
used. These are base for rules and empty strings for
<br>
variant and options.
<br>
<br>
rmlvo/<rules>#<model>#<layout>#<variant>#<options>
<br>
configure the keyboard according to the rmlvo
<br>
(Rules+Model+Layout+Variant+Options) description given
<br>
after the / and separated by #. This can be used to
<br>
fully pass the keyboard configuration of nxagent right
<br>
after the start. Example:
<br>
rmlvo/base#pc105#de,us#nodeadkeys#lv3:rwin_switch
<br>
<br>
If keyboard is omitted the internal defaults of nxagent will be
<br>
used (rules: base, layout: us, model: pc102, empty variant and
<br>
options).
<br>
<br>
Uli
<br>
</p>
</blockquote></div><br></div></div></div>