From misha.cn.ua@gmail.com Thu Mar 14 10:42:43 2019 Received: (at 1369) by bugs.x2go.org; 14 Mar 2019 09:42:45 +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.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,FROM_EXCESS_BASE64,HTML_MESSAGE, URIBL_BLOCKED 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 E6AE95DAED for <1369@bugs.x2go.org>; Thu, 14 Mar 2019 10:42:42 +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 E-m-SQBMBB8w for <1369@bugs.x2go.org>; Thu, 14 Mar 2019 10:42:35 +0100 (CET) Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 1F5D55DAE8 for <1369@bugs.x2go.org>; Thu, 14 Mar 2019 10:42:35 +0100 (CET) Received: by mail-lj1-x230.google.com with SMTP id y9so3916725ljk.6 for <1369@bugs.x2go.org>; Thu, 14 Mar 2019 02:42:35 -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; bh=pr4w7lo5nQYCSGsHPggYqnxuavHADakXKBBr9C0aipU=; b=hSFsfu/XaXkZSp21xc05YVU26mE+DfMPbJHs1z+jeT8HTOQwm+JYCoU6CEQRQpHre5 sj+bm8t0z5b1YjKE/ACtt0x6H5TLI2lPAXlGHlda1XCTmz9O14hEvkcYviP3J6DEsaEa 70W9XPbXwQrOsgDcpCKAHEkMXZIhNYZ1fvD9c2iRgCVlabEy/eVp0Qf8NlrCSkIgwJk7 4rC6sy1DA12aGzbQ6kGOovxc7V5HTUlyGpDhcDa3inElKVzVdzcaWqadWyjhbjIDPBeh dZ7K9oH3hmATchW4U+mNTpYPCJsjsRGvUylJBcbC8kr0/ZDakgLve2stm4U3r1un4Ru4 WxKQ== 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; bh=pr4w7lo5nQYCSGsHPggYqnxuavHADakXKBBr9C0aipU=; b=KFVTuJdvh2jKUCWsKDmPFCx4lIzXqnWZVnwo/oIxXpknnkwgFYvpKJVV5q4fZd6i/l A5uPrY3B5U5w2kmrM328+eDtTBxKIUrFvfrrnZSBVwgLSNFIIk+oApB8WyhbfHUtsp6a f/DXvgbC8xAZZRXCNlIkWP13FKo3PT8MQMZ6KIG/jMBtF7tzyXRvFKSeHLOW8rlUCLQK uL8svPqTHxBC6aVNWuim96al0OLH4zokv5eJTI4oSPDw85L3KHvE+AlDzFDqQxwynoGX Kp6Pcsrdc/PLmRqmUVUdK/mZY6FosPU41dMKflPm1E4R9Zqf+M9M1ciX4QWWPrkq6Hko GjDQ== X-Gm-Message-State: APjAAAWABWvnxs4UfcR0YFXoFyw2nkEvQc0c61DARRGZv2qcF4jhmaXb FLwx/hzmH48MbO4FgnH/9ddpOVYKpKHxfo9PGM0= X-Google-Smtp-Source: APXvYqz7mgotHKUCOfcEpDZpAihcs5AZCLSQ2TimX5YURGtrFoKkryG3Njw8ZenTwGbv7YLbrR7P9KZE67MGVd09xCI= X-Received: by 2002:a2e:2202:: with SMTP id i2mr25145643lji.170.1552556554393; Thu, 14 Mar 2019 02:42:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?0JzQuNGF0LDQudC70L4g0J/QsNC00LDQu9C60LA=?= Date: Thu, 14 Mar 2019 11:42:26 +0200 Message-ID: Subject: Re: [X2Go-Dev] Bug#1369: Bug#1369: Bug#1369: Keys do not release when using Emacs in X2GO Client To: uli42@gmx.de, 1369@bugs.x2go.org Content-Type: multipart/alternative; boundary="000000000000eb1eee05840abdc5" --000000000000eb1eee05840abdc5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Well, just for note, from time to time I observe similar behavior even without NX - when switching between apps with Alt-TAB - TAB key is occasionally not released. Looks like some bug either in kernel, or in Xorg, not sure where exactly. =D0=A7=D1=82, 14 =D0=B1=D0=B5=D1=80. 2019, 08:56 =D0=BA=D0=BE=D1=80=D0=B8= =D1=81=D1=82=D1=83=D0=B2=D0=B0=D1=87 Ulrich Sibiller =D0=BF= =D0=B8=D1=88=D0=B5: > 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 eve= n > 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 Window= s >>> 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 fir= st >>> 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 key= s >> 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 >> >> > _______________________________________________ > x2go-dev mailing list > x2go-dev@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-dev --000000000000eb1eee05840abdc5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Well, just for note, from time to time I observe similar = behavior even without NX - when switching between apps with Alt-TAB - TAB k= ey is occasionally not released.
Looks like some bug eithe= r in kernel, or in Xorg, not sure where exactly.


=D0=A7=D1=82, 14 =D0=B1=D0=B5=D1=80. 2019, 08:56 =D0=BA=D0=BE=D1=80= =D0=B8=D1=81=D1=82=D1=83=D0=B2=D0=B0=D1=87 Ulrich Sibiller <uli42@gmx.de> =D0=BF=D0=B8=D1=88=D0=B5:
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 ma= chines on the other side of the Atlantic ocean - and it worked flawlessly.= =C2=A0

@Yan: you could try set= ting 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 Zhang <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
_______________________________________________
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev
--000000000000eb1eee05840abdc5--