From unknown Tue May 05 13:11:37 2026 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: Ulrich Sibiller , 1369@bugs.x2go.org Resent-From: Ulrich Sibiller Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Thu, 14 Mar 2019 06:55:01 +0000 Resent-Message-ID: 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.155254627817141 (code B ref 1369); Thu, 14 Mar 2019 06:55:01 +0000 Received: (at 1369) by bugs.x2go.org; 14 Mar 2019 06:51:18 +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=-1.9 required=3.0 tests=BAYES_00,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 53CB35DAED; Thu, 14 Mar 2019 07:51:10 +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 X8F9FBmSKbiL; Thu, 14 Mar 2019 07:51:03 +0100 (CET) Received: from mail-vs1-f42.google.com (mail-vs1-f42.google.com [209.85.217.42]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id B2C8C5DAE8; Thu, 14 Mar 2019 07:51:03 +0100 (CET) Received: by mail-vs1-f42.google.com with SMTP id e1so1595438vsp.2; Wed, 13 Mar 2019 23:51:03 -0700 (PDT) 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=TLERy3rhmo5VpEyGtd0RFsF13tvOOxuUoiYEV0UU62w=; b=XPZ8BoYghDHXCPY7RvnPZ8cetGG+iyUvZ88wDGtjlDX0F3gVWw2TXinnORXMgqy8Yw FTitCTDHtTep5n/Hy2Fpdo/bxM1j+CBSQnjFCR2GQWyyOnSBBAnckdU7Y4JGZqAqyHBR Kh+vJt3iDA1SSa7RK8kdnFPTfSlc14Y6/O7YMEFfCugK0AGZIiEhvTRwfmsjv99hrdMC k3Ov1RfQmoryDhkp8c03lSsopT2acjREkuyw7aOKoEO95wUcUWN5pkF8y8eiXIWzN811 M67fN4GILCyCfoVW4DhE+wV+WvjcOreCGR8mxI3BZ+pC07HKnmE02qmrDnPCNF1oNbso aY4g== X-Gm-Message-State: APjAAAWcVxgy8YZhUZ/DaWNezGVtznmkADjzeOMVmWJPN6avOyFPxdp/ c1wDmuElku7bn+pbZXMBuPjfcRZI0ZnEvUXalCo= X-Google-Smtp-Source: APXvYqw4XMjgWieAIfqiNvicuqMxeRVkIgg5gZnn9LsnA2dV7skdF/DqGKyvRjkPwPQf1JiePxdyQ6PTIKEpoL2ODPk= X-Received: by 2002:a67:8452:: with SMTP id g79mr24325819vsd.234.1552546262286; Wed, 13 Mar 2019 23:51:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ulrich Sibiller Date: Thu, 14 Mar 2019 07:50:49 +0100 Message-ID: To: Bob Harold Cc: 1369@bugs.x2go.org, Yan Zhang , submit@bugs.x2go.org Content-Type: multipart/alternative; boundary="0000000000007605f30584085844" --0000000000007605f30584085844 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 schrieb am Do., 14. M=C3=A4rz 2019, 02:50: > > On Wed, Mar 13, 2019 at 5:17 AM Ulrich Sibiller wrote: > >> On Wed, Mar 13, 2019 at 9:10 AM Yan Zhang 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 r= epo. >> >> 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 > > --0000000000007605f30584085844 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You mean NX, I guess, not X2 (there's no such protoco= l). 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.=C2=A0

@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=C3=A4rz 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 Z= hang <kriszhyan@gmail.com> wrote:

>> > I am using Emacs 24.5.1 with x2go client version 4.1.2.0 in W= indows 10. My server OS is Ubuntu 16.04 and the x2goserver comes from the P= PA 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+s= pace") before moving cursor. The client will only stuck if I first sta= rt 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.

>=C2=A0 I tried "xev -event keyboard" in a XFCE session and di= d 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.= =C2=A0 It is possible that holding the keys for a few seconds, with auto-re= peat, has buffered enough copies of the keystroke to scroll the file all th= e way to the end, even after you let go.=C2=A0 Is that possible?
=
--=C2=A0
Bob Harold
=C2=A0
--0000000000007605f30584085844--