X2Go Bug report logs - #1339
Incorrect keyboard keys when connecting to local desktop session

version graph

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

Reported by: Bryan Roessler <bryanroessler@gmail.com>

Date: Fri, 2 Nov 2018 16:45:07 UTC

Severity: normal

Found in version 4.1.0.1

Full log

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

Received: (at 1339) by bugs.x2go.org; 3 Dec 2018 23:58:37 +0000
From bryanroessler@gmail.com  Tue Dec  4 00:54:53 2018
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.7 required=3.0 tests=BAYES_50,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE autolearn=ham
	autolearn_force=no version=3.4.2
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 6E5295DAE8
	for <1339@bugs.x2go.org>; Tue,  4 Dec 2018 00:54:44 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tjt5cFg6vEVS for <1339@bugs.x2go.org>;
	Tue,  4 Dec 2018 00:48:01 +0100 (CET)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id D12F45DAEB
	for <1339@bugs.x2go.org>; Tue,  4 Dec 2018 00:47:52 +0100 (CET)
Received: by mail-lj1-x236.google.com with SMTP id t9-v6so13111364ljh.6
        for <1339@bugs.x2go.org>; Mon, 03 Dec 2018 15:47:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:from:date:message-id:subject:to;
        bh=gAYi1FYzrsc053Pfh4TPZtS0vAlM6TdHFC6QyH0qOBU=;
        b=Enle2S8mBjSyy88Wqs6RrA10QD4pWXHCbPY6A+qXNrBtwke5+GOA6rm1Nt3zRD6g6M
         AKtW4BZkuwnsSHibccefIIfEG/HU8hi2x77BdpFPRZKCmuqA+snubkdrmNS56tI54joJ
         mm438SqT0Z/73kVI0lfBYtwE5nnZlYfBtuUC1Xkl7nxY6eFPjgWOhJQKYFEP+zvJ0x3c
         yx1gisMNhNzRMoKdFrpRTBMNYX1VoFTV4DvNR6mDADSEh6B3H+VZ+1FjK6y01/JzIfuF
         lW01674OUE6Scq5ahDCldCM/Ce/vmdKu7COV9FxpRDORmFADFhfVICXiQ0WEyCUFL4su
         5Vew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=gAYi1FYzrsc053Pfh4TPZtS0vAlM6TdHFC6QyH0qOBU=;
        b=pc32Y5NgEhvZrRHY+NvTfqjtMNVeWbGMFVh6nnNj3qeTaNsAt35IC0hB3xjRcXsIPm
         ZFv8ZGMhZoriRpq8n5nFcSWrb5m5vdN6dvm7Pb9MAtVYPOs+XOt26lb3da4QautzHpLv
         YWJjyVCgEUua9dWPLRbaKPR5gQ2XI/skmonYjLiBO0jdVeCngzktb+jmhnIff5GgVZDc
         1dNp5+8uanM3ABFreCBeguZ0OGgJTjjv7rwqoyGTQ1FHfQxTk3cGtwuKimtfla1qrA+V
         uDzSUAfPyOTTIIfT4m4KxpUVAmaTMxmxcYgmuGnIb7odWgFpx0mQ0YTiOk+NSriCwl31
         diuQ==
X-Gm-Message-State: AA+aEWYmaoqOhwY450T/MJVene7khnrCrTUYjjiZ5ioqdedGTqahgU8F
	ZUemFrf/MY2Esa6rk0m3xWI/e2MDoUPsytlooEWT8NRh
X-Google-Smtp-Source: AFSGD/WpOlskQVm5eFULW8OKHbfjaRmD2DE9ubR9wArWHDpMkhaBIkci/izmdYSycOb/ZPdfqe41yna1iJ/fP87ouls=
X-Received: by 2002:a2e:9603:: with SMTP id v3-v6mr9707545ljh.15.1543880871553;
 Mon, 03 Dec 2018 15:47:51 -0800 (PST)
MIME-Version: 1.0
From: Bryan Roessler <bryanroessler@gmail.com>
Date: Mon, 3 Dec 2018 18:47:15 -0500
Message-ID: <CADjPr8RaATYBZ-J3dpHO36WY_eaoh_iFrZjRLJgCE2wddrO5wA@mail.gmail.com>
Subject: 
To: 1339@bugs.x2go.org
Content-Type: multipart/alternative; boundary="000000000000ecb0d2057c26c687"

[Message part 1 (text/plain, inline)]
I have found that the issue appears to be related to the keycodes setting.

Running:

>setxkbmap -model pc105 -layout us -keycodes "xfree86+aliases(qwerty)"

Gets the keyboard keys to work properly again.

Subsequently, running:

>setxkbmap -model pc105 -layout us -keycodes "evdev+aliases(qwerty)"

Results in the keyboard keys not working.

However, the output of setxkbmap -print does not change after that command
is issued even though it fixes the problem:

>setxkbmap -model pc105 -layout us -keycodes "evdev+aliases(qwerty)" ###
keyboard keys stop working properly
>setxkbmap -print
xkb_keymap {
    xkb_keycodes  { include "evdev+aliases(qwerty)"    };
    xkb_types     { include "complete"    };
    xkb_compat    { include "complete"    };
    xkb_symbols   { include "pc+us+inet(evdev)"    };
    xkb_geometry  { include "pc(pc105)"    };
};
>setxkbmap -model pc105 -layout us -keycodes "xfree86+aliases(qwerty)" ###
keyboard keys start working properly
>setxkbmap -print
xkb_keymap {
    xkb_keycodes  { include "evdev+aliases(qwerty)"    };
    xkb_types     { include "complete"    };
    xkb_compat    { include "complete"    };
    xkb_symbols   { include "pc+us+inet(evdev)"    };
    xkb_geometry  { include "pc(pc105)"    };
};

I would assume that changing the keycodes setting would also change the
xkb_keycodes returned from setxkbmap. I do not understand why this bug is
happening, and unfortunately my understanding of X keyboard mappings goes
no further. I wish there was a way to pass this keycodes directive in x2go,
but I do not know which component of this setup is the guilty party.

Hopefully this can at the least help someone with the same issue.

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Sat Apr 20 05:00:06 2024; 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.