X2Go Bug report logs - #1369
Keys do not release when using Emacs in X2GO Client

version graph

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

Reported by: Yan Zhang <kriszhyan@gmail.com>

Date: Mon, 28 Jan 2019 06:00:04 UTC

Severity: normal

Found in version 4.1.2.0

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#1369: [X2Go-Dev] Bug#1369: Bug#1369: Keys do not release when using Emacs in X2GO Client
Reply-To: Yan Zhang <kriszhyan@gmail.com>, 1369@bugs.x2go.org
Resent-From: Yan Zhang <kriszhyan@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: Thu, 14 Mar 2019 12:05:02 +0000
Resent-Message-ID: <handler.1369.B1369.155256483130148@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 1369
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
Received: via spool by 1369-submit@bugs.x2go.org id=B1369.155256483130148
          (code B ref 1369); Thu, 14 Mar 2019 12:05:02 +0000
Received: (at 1369) by bugs.x2go.org; 14 Mar 2019 12:00:31 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-2.0 required=3.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,URIBL_BLOCKED
	autolearn=unavailable autolearn_force=no version=3.4.2
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 5BE775DAED;
	Thu, 14 Mar 2019 13:00:22 +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 VXaaH32D76qT; Thu, 14 Mar 2019 13:00:12 +0100 (CET)
Received: from mail-ua1-x934.google.com (mail-ua1-x934.google.com [IPv6:2607:f8b0:4864:20::934])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 63A3B5DAE8;
	Thu, 14 Mar 2019 13:00:12 +0100 (CET)
Received: by mail-ua1-x934.google.com with SMTP id 46so309510uan.8;
        Thu, 14 Mar 2019 05:00:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=ZBHq99jSIU1KREIdFt5TowlZAppibpuJGCXexDq9QsE=;
        b=NCSNK/Kg1puSccIa6IeouESKSGZjMpMJSPcLIrSEct6/MEUZ0DDrQQMkvltC6a7RGU
         Y1BFFvXgqqbrnG7oGvR7v1tqXTTNYA/FTF/4Ng3Vma2jwLM2r/hlX8VmRSpMtWRyT/FB
         42LLV4LJSOeW+dSFteWXj5SSfSuuxrDl4biBK6RHIv51YB2SsvouAfClUzbjjUP9BtRV
         DA4SWvPdH/yBjlMzQHTndMd5SgEEpCSxmddA/XxfZsi9W7onkogJpmeaFy5BqkzsFjTt
         jXYv/FqkGWi0CFjh2188Xdk7rUDrk+U41iS1mT0V4F4bhJxaB8fk6DHnHDk6qB/mGYhW
         nh9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=ZBHq99jSIU1KREIdFt5TowlZAppibpuJGCXexDq9QsE=;
        b=t/2sNe7OLEjqugx2esVqsNOvy6O81aD2YN8r5dI7Ognj0KoaiY4YHgN1OCDDuHNhoa
         D/82tksQ8Yaf4xDruyovPtcrnOSnUb5RCcTqJrho4D5eOvMS3ol2gQTEMkILqCccyqUB
         VIVBYBVeo3fuWXwbiGU5N9P1SNfsM3BRWTcXzQpVg+bcF4aXTU89H7aMQ1poaDNk3oEi
         2g4uQFyUxFZVbHsZUydRkoShnL5PkqkhvlZDl9o+qnYrQpysz2/GNf1YxoaRoLUxziVp
         m3mrXFoD2r/wojGYAczgnvnaXsK/d8mEc7bUzF5ljSctMnmvv3qg4li9I3ahQfQYPgLS
         d38g==
X-Gm-Message-State: APjAAAW1VljDj2eZDztGRnGLOrG/2Jzm+SPAIvXkQs0PTKL6vgvTEwHm
	zGZlRpNaoQFWSHwto+ES47z8rufCahjZvHf5dnM=
X-Google-Smtp-Source: APXvYqx8rhV0KLw0cUoH7Yc8qDYsGiNlKZWL/KBZRhjrWnjww47Ui4dJiG+/7jbHVIUipBQZjmLwFjuKtVLxBFYs5cs=
X-Received: by 2002:ab0:6513:: with SMTP id w19mr25818925uam.19.1552564811186;
 Thu, 14 Mar 2019 05:00:11 -0700 (PDT)
MIME-Version: 1.0
References: <CA+E0ge3vGXaAsgBbT3hGe24Q2vQ11+zhgd1yg+M-cZk1vjs0wA@mail.gmail.com>
 <CANVnVYLNoy8bA3v2pjuAfLqKrp2wxXVFzFFY7Bzz5=vT8Q7V+g@mail.gmail.com>
 <CA+E0ge0=wr724NEKQTppc_R+r7MEbkZWutujy-x-b_anHLjPSQ@mail.gmail.com>
 <CANVnVYJOZ+jfWXykOxBAmVCUKj5mKvrqqvUKRSAva8=_Myun2w@mail.gmail.com>
 <CAKJ-5_8QN-cOexrwKdPeZsmrK_8M8PP-vrAHoT4K8TspVKSoZQ@mail.gmail.com> <CANVnVY+y4X-2iukbZBjgLudPDS65QnJnNGJji7rXKro+X7uShA@mail.gmail.com>
In-Reply-To: <CANVnVY+y4X-2iukbZBjgLudPDS65QnJnNGJji7rXKro+X7uShA@mail.gmail.com>
From: Yan Zhang <kriszhyan@gmail.com>
Date: Thu, 14 Mar 2019 19:59:59 +0800
Message-ID: <CA+E0ge2mW=uCRdm-dm1PwRvf04QgSVZb97s-wji4uxRYyXhfVQ@mail.gmail.com>
To: Ulrich Sibiller <uli42@gmx.de>
Cc: Bob Harold <bobh@halfgoat.com>, 1369@bugs.x2go.org, submit@bugs.x2go.org
Content-Type: multipart/alternative; boundary="0000000000000fc6a705840caa52"

[Message part 1 (text/plain, inline)]
Hi Uli,

I found a temporary solution. If I disable the transient mark mode, under
which the selected region is highlighted, this issue goes away. So I guess
the issue is related to events generated by rendering the highlighted
region. And one thing I forgot to mention is that if I start emacs without
GUI (i.e., emacs -nw), I do not have this issue.

On the other hand, I have tried to use ADSL/ISDN, change my emacs version
to both 26.1 and 24.3.1, and upgrade NX to the nightly build. None of these
has any effect.

Thanks and regards,
Yan

On Thu, Mar 14, 2019 at 2:51 PM Ulrich Sibiller <uli42@gmx.de> wrote:

> You mean NX, I guess, not X2 (there's no such protocol). However: I am
> using NX over two chained WANs without such problems. For some time I even
> used it for working on machines on the other side of the Atlantic ocean -
> and it worked flawlessly.
>
> @Yan: you could try setting the connection type to ADSL or even ISDN and
> retry.
>
> Uli
>
> Bob Harold <bobh@halfgoat.com> schrieb am Do., 14. März 2019, 02:50:
>
>>
>> On Wed, Mar 13, 2019 at 5:17 AM Ulrich Sibiller <uli42@gmx.de> wrote:
>>
>>> On Wed, Mar 13, 2019 at 9:10 AM Yan Zhang <kriszhyan@gmail.com> wrote:
>>>
>>> >> > I am using Emacs 24.5.1 with x2go client version 4.1.2.0 in Windows
>>> 10. My server OS is Ubuntu 16.04 and the x2goserver comes from the PPA repo.
>>>
>>> You could try updating your nx-libs to nightly and retry:
>>> https://sunweavers.net/blog/node/20
>>>
>>> > The difference is whether I start mark region (by hitting
>>> "ctrl+space") before moving cursor. The client will only stuck if I first
>>> start mark region and then hold cursor-moving keys like "ctrl+n" or
>>> "ctrl+p" for a few seconds.
>>>
>>> Ok, understood. But still not replicable for me.
>>>
>>> >  I tried "xev -event keyboard" in a XFCE session and did not observe
>>> any missing keystrokes.
>>>
>>> Nor did I. So maybe this is bug in emacs. I tested with 24.3.1, can
>>> you downgrade?
>>>
>>> Uli
>>>
>>
>> Just a thought - there is some lag in the screen updates from the remote
>> host when using a protocol like x2.  It is possible that holding the keys
>> for a few seconds, with auto-repeat, has buffered enough copies of the
>> keystroke to scroll the file all the way to the end, even after you let
>> go.  Is that possible?
>>
>> --
>> Bob Harold
>>
>>
>

-- 
Yan

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

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 15:26:45 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.