X2Go Bug report logs - #674
keycode -> keycode translation harmful (makes configuration complex)

Full log

Message #23 received at 674@bugs.x2go.org (full text, mbox, reply):

Received: (at 674) by bugs.x2go.org; 7 Dec 2014 23:07:29 +0000
From ulrich.sibiller@gmail.com  Mon Dec  8 00:07:29 2014
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: *
X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_40,FREEMAIL_FROM,
	FREEMAIL_REPLYTO,FREEMAIL_REPLYTO_END_DIGIT,T_DKIM_INVALID,URIBL_BLOCKED
	autolearn=no version=3.3.2
Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id DF9075E0E0
	for <674@bugs.x2go.org>; Mon,  8 Dec 2014 00:07:28 +0100 (CET)
Received: by mail-lb0-f177.google.com with SMTP id b6so2858828lbj.22
        for <674@bugs.x2go.org>; Sun, 07 Dec 2014 15:07:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:reply-to:in-reply-to:references:from:date:message-id
         :subject:to:content-type:content-transfer-encoding;
        bh=RkW4FyP+GYKrWkx4KXwa6K1eo/y9MGj/ZshOgq8ng34=;
        b=GMjyV8Bv65ew2CWCHvo3nOKRHk+0UcKeBYXk6dNeRSyTx9724imwdEamKwgBP5XEUS
         /ZklJU0PnHocDRJrvg9i804+tJr4YpX0jXIDtEq12QI2QGZ1tLSFXfRwXz4OlHqZEIcg
         whb8AbBXvSX3ss2VQS5n05nUBp1oHGRiXOFp1YfPgwsLKFqVgu0+cgWjI1VKmCmHfWEW
         Y1IvlbO1rYgZ0hm3wXi9kSeIjNRQcZ1QXpOpHgQJc8hX9XKzMj1puScp5uypvoXmSdA7
         e+uypcyDUjhW8pm/yRc8GTzSF9UZVkfPs+tTNVSgO7SC9yedbp6NN/qhWmB84kO9P+aa
         l24Q==
X-Received: by 10.152.36.232 with SMTP id t8mr13555949laj.6.1417993647929;
 Sun, 07 Dec 2014 15:07:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.89.101 with HTTP; Sun, 7 Dec 2014 15:07:07 -0800 (PST)
Reply-To: uli42@gmx.de
In-Reply-To: <5483D272.8020008@backsla.sh>
References: <54654F43.1020306@backsla.sh> <handler.674.B.141592592311413.ack@bugs.x2go.org>
 <5483D272.8020008@backsla.sh>
From: Ulrich Sibiller <ulrich.sibiller@gmail.com>
Date: Mon, 8 Dec 2014 00:07:07 +0100
Message-ID: <CANVnVYK+YXWc_FJqeaEG325AJtGXYSfpD_zx+vbvESOt5WudxA@mail.gmail.com>
Subject: Re: [X2Go-Dev] Bug#674: Acknowledgement (keycode -> keycode
 translation harmful (makes configuration complex))
To: Robert Siemer <Robert.Siemer@backsla.sh>, 674@bugs.x2go.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Dec 7, 2014 at 5:07 AM, Robert Siemer <Robert.Siemer@backsla.sh> wrote:
> On x2go session startup, the x2go Xserver [2] does a superficial
> investigation of what keyboard is used on the local Xserver [1] and sets up
> an incomplete keycode translation to a keyboard known as “xfree86”. It
> further creates an imperfect copy of the XKB configuration from [1] to [2].
> The _XKB_RULES_NAMES property on [2] is set to rules=xfree86, model = pc???,
> layout = us(?) [I forgot the details].
>
> Why is it a superficial investigation? – It takes the rules name from
> _XKB_RULES_NAMES and deducts the resulting keycodes directly from that (I
> believe). Even though in a common setup rules name “evdev” results in one
> specific set of keycodes and rules name “xfree86” in another specific set of
> keycodes, this is not a must.
>
> Why is the keycode translation incomplete? – As far as I observed it,
> “unusual” or unknown keycodes are not translated and passed as-is.
>
> Why is the XKB configuration copy imperfect? – I did a XKB dump on the local
> Xserver [1] and the x2go Xserver [2] after starting a new session. Keys with
> four levels of symbols turned into two-level-keysyms. – _Loading_ (i.e.
> xkbcomp/setxkbmap) a four-level configuration is no problem, though.
>
> Note: the imperfect copy of the XKB configuration is almost always useless,
> because the copied configuration does not match the new (translated)
> keycodes!
>
> Resuming an x2go session triggers the same superficial keyboard
> investigation, the translation kicks in again, but the XKB configuration is
> not touched (i.e. is not copied from [1] to [2]).
>
> Deleting the _XKB_RULES_NAMES property before session startup/resume or
> setting the first part (that is the “rules” part) to some unknown string
> results in untranslated keycodes.

I am not sure if I am getting this right. Will using xkbcomp on the
local server, pushing the result to the nxagent and loading it there
result in a clean keyboard setup or not? Do we need to disable setting
up the translation within the nx code to make that work?

Uli

BTW: You can find the code for the keycode translation in
nx-x11/programs/Xserver/hw/nxagent/Keyboard.c. It seems some kind of
translation from evdev to pc105 is done. You can also see that if
there is no "xfree86" rules file the one called "xorg" is used instead
(if available, of course).

Send a report that this bug log contains spam.