From kriszhyan@gmail.com Wed Mar 13 09:10:17 2019 Received: (at 1369) by bugs.x2go.org; 13 Mar 2019 08:10:19 +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=-0.1 required=3.0 tests=BAYES_20,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 659FD5DAE8; Wed, 13 Mar 2019 09:10:17 +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 GkAao1EUcgBT; Wed, 13 Mar 2019 09:10:03 +0100 (CET) Received: from mail-vs1-xe43.google.com (mail-vs1-xe43.google.com [IPv6:2607:f8b0:4864:20::e43]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 84F7E5DA8B; Wed, 13 Mar 2019 09:10:03 +0100 (CET) Received: by mail-vs1-xe43.google.com with SMTP id z6so477668vsc.0; Wed, 13 Mar 2019 01:10:03 -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=LJJVAs5q9PeK/7v4t/tESQa9+0xruwx8Wu6Ko4wYYHc=; b=SHYZTFKKUTzT/wa0DjyuHFas5SqybfxUSUXu0xB0qzS29caB0hhy8UQFcmkH3LYBWl oZsoteBuyP1eJGenzWeTkObb+NVfdpTghIpQspo1uID2x/3LL5VpK7s9ccejVEuwidFM 9iaHA+NzAbITgUeZxWRhWMP3Jvf1mOQovOusPktwd4BryxXjtgfslKlzaRDo7y3mf7QF ZJI5pWMm7VrBUCCG1B7cycOpI6rohThVMcWKm8viOUD5CQ34tBSQxeoQ9ZALQRW91dVy Sshx48giTk2PetLJ7bocbNHmW4QAqGMy8X2qXoSk/IS04kEbhIPh6MhynO0BaPIqVY8J wMuQ== 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=LJJVAs5q9PeK/7v4t/tESQa9+0xruwx8Wu6Ko4wYYHc=; b=WAX97o3FoJ6G92n/FRHg+n9tn0je+svc+95us+jcRLraputWr2f744ILMbu0/syriD 8iHYsILzeemfDlxcins4rrT7Ozlqp7gWUUQ/FhxQm5/6I3Zbnp8iSqFEm1uWct1Bs7DM R4NtQmtuJzVU72dlpco1UJz0pQaikFnypZuL9JeNtTUwAPVHUanKk2MOmEgD54Hxfn5r 85drEneGpyrfDdIryaxVUJMP12nfuiSrHFqhKm0JPiRUHKKb8fg4jVcsSWv/JbcZyogB qMVhMLPBm0jEx2Aaf5ZhjfOJIqSd8R9n4cOVE7EJSobv2aUewAj+LfT616dxW3uT2CGE Cfjw== X-Gm-Message-State: APjAAAXpMawawXqTLbKBs7RT88wPh6UXz0FEnzRGEq1hRF78RECo9/YT 44Jp6VN92Kc/tne8tET52fyEhTKuVp4qqmuwqGY= X-Google-Smtp-Source: APXvYqycl7tLHCHt3UmRWUU2VCyZYSjh+Po2Mzsmyi/ZKFxzImAqAFMppZo9aNMVOwmS5xivbFzyHvkLJwNm7TUU+Kc= X-Received: by 2002:a67:69d8:: with SMTP id e207mr18267657vsc.94.1552464602120; Wed, 13 Mar 2019 01:10:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Yan Zhang Date: Wed, 13 Mar 2019 16:09:51 +0800 Message-ID: Subject: Re: [X2Go-Dev] Bug#1369: Keys do not release when using Emacs in X2GO Client To: uli42@gmx.de Cc: 1369@bugs.x2go.org, submit@bugs.x2go.org Content-Type: multipart/alternative; boundary="00000000000022c5900583f5554b" --00000000000022c5900583f5554b Content-Type: text/plain; charset="UTF-8" Hi Ulrich, On Tue, Mar 12, 2019 at 8:29 PM Ulrich Sibiller wrote: > On Tue, Mar 12, 2019 at 12:38 PM Yan Zhang wrote: > > > > Package: x2goclient > > Version: 4.1.2.0 > > > > 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. > > > > The problem happens if I hit "ctrl+space" to start mark region in Emacs > and then press down "ctrl+n" to scroll down the region for a few seconds. > Usually after I release "ctrl+n", Emacs will leave the currently marked > region for further commands. But in the reported version of client, Emacs > keeps scrolling down until it reaches the end of the file. There is no way > to stop it within Emacs (e.g., "ctrl+g"). > > > > I have tried to move the cursor by keeping "ctrl+n" pressed down. This > issue does not happen after I release the key. > > I do not get the difference between this and the description above. > Please explain! > > 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. > > This issue happens when the session type is either "XFCE" or "published > application". I have not tested other session types as I do not have an > environment for that. And client version 4.1.1.1 does not seem to have this > issue. > > Please run "xev -event keyboard" inside the session and check if you > see all the KeyPress and KeyRelease events for you keys. If anyone is > missing this could explain your issue. > > Uli > I tried "xev -event keyboard" in a XFCE session and did not observe any missing keystrokes. Thanks and regards, Yan --00000000000022c5900583f5554b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Ulrich,

On Tue, Mar 12, 2019 at 8:29 PM= Ulrich Sibiller <ulrich.si= biller@gmail.com> wrote:
On Tue, Mar 12, 2019 at 12:38 PM Yan Zhang <kriszhyan@gmail.com> wr= ote:
>
> Package: x2goclient
> Version: 4.1.2.0
>
> 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.<= br> >
> The problem happens if I hit "ctrl+space" to start mark regi= on in Emacs and then press down "ctrl+n" to scroll down the regio= n for a few seconds. Usually after I release "ctrl+n", Emacs will= leave the currently marked region for further commands. But in the reporte= d version of client, Emacs keeps scrolling down until it reaches the end of= the file. There is no way to stop it within Emacs (e.g., "ctrl+g"= ;).
>
> I have tried to move the cursor by keeping "ctrl+n" pressed = down. This issue does not happen after I release the key.

I do not get the difference between this and the description above.
Please explain!


The difference is whether I start mark= region (by hitting "ctrl+space") before moving cursor. The clien= t 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.
=
=C2=A0
> This issue happens when the session type is either "XFCE" or= "published application". I have not tested other session types a= s I do not have an environment for that. And client version 4.1.1.1 does no= t seem to have this issue.

Please run "xev -event keyboard" inside the session and check if = you
see all the KeyPress and KeyRelease events for you keys. If anyone is
missing this could explain your issue.

Uli

=C2=A0I tried "xev -event keyb= oard" in a XFCE session and did not observe any missing keystrokes.

Thanks and regards,
Yan
--00000000000022c5900583f5554b--