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

version graph

Package: x2goserver; Maintainer for x2goserver is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goserver is src:x2goserver.

Reported by: Robert Siemer <Robert.Siemer@backsla.sh>

Date: Fri, 14 Nov 2014 00:50:02 UTC

Severity: normal

Found in version 4.0.1.18

Full log

đź”— View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#674: Fwd: [X2Go-Dev] Bug#674: Acknowledgement (keycode -> keycode translation harmful (makes configuration complex))
Reply-To: Ulrich Sibiller <uli42@gmx.de>, 674@bugs.x2go.org
Resent-From: Ulrich Sibiller <uli42@gmx.de>
Original-Sender: ulrich.sibiller@gmail.com
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Tue, 16 Dec 2014 09:45:01 +0000
Resent-Message-ID: <handler.674.B674.141872282823910@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 674
X-X2Go-PR-Package: x2goserver
X-X2Go-PR-Keywords: 
Received: via spool by 674-submit@bugs.x2go.org id=B674.141872282823910
          (code B ref 674); Tue, 16 Dec 2014 09:45:01 +0000
Received: (at 674) by bugs.x2go.org; 16 Dec 2014 09:40:28 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM,
	T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from mail-la0-f51.google.com (mail-la0-f51.google.com [209.85.215.51])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id F30D05DB1C
	for <674@bugs.x2go.org>; Tue, 16 Dec 2014 10:40:26 +0100 (CET)
Received: by mail-la0-f51.google.com with SMTP id ms9so10908515lab.10
        for <674@bugs.x2go.org>; Tue, 16 Dec 2014 01:40:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date:message-id
         :subject:to:content-type:content-transfer-encoding;
        bh=u7N8pkXpuPti5W5Oi9yk9v5jl1oRu+wpayXAmAHGC70=;
        b=VqBIl8Lb+mbvhx7BxnWcyx5Tx0lo6DamzqJIoCivCM0wylZkxnjN4bNridTwjhm3uF
         4EbzZAr4KlR9f0Z+9dSP7DAlZJQeDpnJZe1D9/aIfKlAtnNAP17LaOZ7vyz9yer+C/mc
         Pg8abw5Gix5b8DlJmSzVSVv7CciMpTwlHeEoShpKalSm9RbJq4DIFSxDyJiIFGz/XQJC
         BvpnRjEHxNBmbnJbsvy/grWlp23GuUC1IkHEvtK8huVp6XtYz9whxZrfbW+bTrCpikWk
         KqObHOdLoRqxY/97rKAJA31E4uuaIDqqWbH+4B45RYkOdJ9SswO7IS9M9xFrJZz2uCfG
         UPNQ==
X-Received: by 10.112.172.194 with SMTP id be2mr7010280lbc.53.1418722826472;
 Tue, 16 Dec 2014 01:40:26 -0800 (PST)
MIME-Version: 1.0
Sender: ulrich.sibiller@gmail.com
Received: by 10.112.89.101 with HTTP; Tue, 16 Dec 2014 01:40:06 -0800 (PST)
In-Reply-To: <CANVnVYL1XC9y7bX22Zg4o2Shfw8vbfR-htHSM=wGrMh2Fr78nQ@mail.gmail.com>
References: <54654F43.1020306@backsla.sh> <handler.674.B.141592592311413.ack@bugs.x2go.org>
 <5483D272.8020008@backsla.sh> <CANVnVYK+YXWc_FJqeaEG325AJtGXYSfpD_zx+vbvESOt5WudxA@mail.gmail.com>
 <548B8C0E.7020701@backsla.sh> <CANVnVYL1XC9y7bX22Zg4o2Shfw8vbfR-htHSM=wGrMh2Fr78nQ@mail.gmail.com>
From: Ulrich Sibiller <uli42@gmx.de>
Date: Tue, 16 Dec 2014 10:40:06 +0100
X-Google-Sender-Auth: tbj6HEausJvv-_yBfOZrhzXYo3E
Message-ID: <CANVnVYJMqPDcpm2CsNoE0CFobxVoXXnYL6tpohZh49Az-_d2vA@mail.gmail.com>
To: 674@bugs.x2go.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 13, 2014 at 1:45 AM, Robert Siemer <Robert.Siemer@backsla.sh> wrote:

> If the translation is on, you get a skewed setup.
>
> Note that the x2go (with the setting of “do nothing”) does a non-perfect
> copy with the same effect: if the translation is effective, the keyboard is
> skewed and you are force to load at least “something” to fix XKB. If the
> translation is off, you “only” need to load XKB configuration if that
> non-perfect copy annoys you...

> Thanks for the pointer! I had a look at it. As I suspected: the translation
> is “bad”. Sometimes two different keycodes are translated to the same
> keycode. How are you supposed to tell them apart on the remote side? You
> can’t.
>
>> It seems some kind of translation from evdev to pc105 is done.
>
> The naming is a little funny: the keycodes generated by the kernel before
> evdev were not called like that, were they?

I don't think so.

>> Do we need to disable setting
>> up the translation within the nx code to make that work?
>
> That would be great as a first step.

I was wondering why this translations had been introduced. It emerged
between nxagent 3.2.0-10 and 3.3.0-9. The changelog between these
releases contains (among others) these changes:

nxagent-3.3.0-9

- Changed Keyboard initialization and reset. This change should fix
  TR11F02129, TR11F02131, TR11F02132.

nxagent-3.3.0-4

- Fix the XKB map load in the case of 64 bit server.

nxagent-3.3.0-3

- Fixed TR10F02119. If the remote X display is using evdev keyboard
  then copy maps from remote.

nxagent-3.2.0-12

- Fixed TR08E01814. Added shadow keymap initialization in order to
  enable nxcompshad to translate keycodes across different layouts.

So it MIGHT have been introduced mainly for shadow sessions. The
TR10F02119 refers to Ubuntu 8.10, which - according to some other
posts I found - is the version that introduced evdev. So the fix that
solved evdev problems is causing problems when evdev is enabled.

I also looked at the source and found that clearing the property seems
to be the only way to disable the translation. (apart from disabling
XKB completely).

Uli

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Sun Dec 7 21:28:58 2025; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.