From unknown Tue May 05 13:56:08 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: Yan Zhang , 1369@bugs.x2go.org Resent-From: Yan Zhang Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Mon, 18 Mar 2019 02:20:02 +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.15528754287777 (code B ref 1369); Mon, 18 Mar 2019 02:20:02 +0000 Received: (at 1369) by bugs.x2go.org; 18 Mar 2019 02:17:08 +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=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 737A05DAE9; Mon, 18 Mar 2019 03:17:04 +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 v8Myeo-HHMor; Mon, 18 Mar 2019 03:16:55 +0100 (CET) Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 0DA625DAE8; Mon, 18 Mar 2019 03:16:55 +0100 (CET) Received: by mail-vs1-xe2d.google.com with SMTP id e1so7556155vsp.2; Sun, 17 Mar 2019 19:16:54 -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=B7VAQLwOVD63ur7DDhQfpyYGNflgKfcHxUtolGspJpA=; b=gEMkPWDAflk0rgORPfK6v1Eo02Gb/mwIgyll7kgRz/1DKr9SpHfqWto42v+vZ8nMy3 EWJ7DVx8KogKu6zNEgVRJBgIde+xd/WNxmjBvXKtQa5GtBe/FJCVdtQo/l/5MbA9VT8i 7Ft+F8lpQwetxGNT4QVNFie7AGFuGnPthvVd7OXlFAdOOICJWQWLohpNpQXv1IVKVb4m gHyNsKrANLeAsbp/uMlrConOEwAkRVImztSVT0gKF/YQzptkVsTHqdb/o3xbltJiWPHz ThBc4NbkJn1TeQY40jTbNl89RfcdYzhoddm0PLBZcCgCFBSrKRWSyMGUFOpX0UKoTOCn W5NQ== 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=B7VAQLwOVD63ur7DDhQfpyYGNflgKfcHxUtolGspJpA=; b=Ef9tOcqKVDCbdHOqeajQxlVQTaCAgEbQFvW3PVAxwX8LtIgIWdAdMpXk7IbppcPbIZ T3QHlAVL1hfNufQO/JjWgwwtEgLQDAL469925MkkcA7VafjnhR16hqFySw3Noq7Lo+GO S1Iav0YYrjRKoK3SVCwDw4KVqscz6K/6/Rl2bcIJTEdF7brMaS0cTgB0OQCVkYAjoLty z+L9CT3fB8KxXzAQGWydpM89+wdA3z5un7eEv6lWSDbimarzVBueZgCV+WL3KaAAuBlp aKnOXDlWE7YE2T3rZWrqYL5mzyxcHDEvFFp3fU3gLC5iNukwn3eB6sNFt13hxx9hBn68 IQZw== X-Gm-Message-State: APjAAAUmc+VV6o3oX6nwdJdjEyhol5ZWs+RISyYnNr3tVJ8bg0riCNUJ KioL3g2iuxv/2xHlDnLAzxcTMaSKURK4v8Y2LQ4= X-Google-Smtp-Source: APXvYqzTp+Uh1kj2o5c+d1x4ksR8LltI5Gf3GufNcgfvIKSsBnAIS8AS6PjRl4cYS66C1zBa+9522P/Y2oLJSegyp1c= X-Received: by 2002:a05:6102:450:: with SMTP id e16mr2528701vsq.94.1552875413779; Sun, 17 Mar 2019 19:16:53 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Yan Zhang Date: Mon, 18 Mar 2019 10:16:42 +0800 Message-ID: To: Ulrich Sibiller Cc: Bob Harold , 1369@bugs.x2go.org, submit@bugs.x2go.org Content-Type: multipart/alternative; boundary="0000000000006b3d50058454fb81" --0000000000006b3d50058454fb81 Content-Type: text/plain; charset="UTF-8" Hi Uli, Sorry for the slow reply. For my XFCE sessions, turning on "-extension GLX" seems to solve the problem. But under "published applications" mode, the issue is still there. Thanks and regards, Yan On Sat, Mar 16, 2019 at 6:54 AM Ulrich Sibiller wrote: > On Thu, Mar 14, 2019 at 1:00 PM Yan Zhang wrote: > > > 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. > > So this indicates that it probalby is connected to drawing. If this > happens via images for some reason it might explain the problem. > > Please perform this test for me: Edit /etc/x2go/agent.options on the > server and ensure that the following line is active (no leading '#'): > > X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension GLX" > > Then start a new session (with transient mark mode enabled) and retry. > Is that working better? > > Uli > -- Yan --0000000000006b3d50058454fb81 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Uli,

Sorry for the slow reply. For m= y XFCE sessions, turning on "-extension GLX" seems to solve=C2=A0= the problem. But under "published applications" mode, the issue i= s still there.

Thanks and regards,
Yan

On Sat, Mar 16, 2019 at 6:54 AM Ulrich Sibiller <uli42@gmx.de> wrote:
On Thu, Mar 14, 2019 at 1:00 PM Yan Zhang <kriszhyan@gmail.com> wrote:

> I found a temporary solution. If I disable the transient mark mode, un= der which the selected region is highlighted, this issue goes away. So I gu= ess the issue is related to events generated by rendering the highlighted r= egion. And one thing I forgot to mention is that if I start emacs without G= UI (i.e., emacs -nw), I do not have this issue.

So this indicates that it probalby is connected to drawing. If this
happens via images for some reason it might explain the problem.

Please perform this test for me: Edit /etc/x2go/agent.options on the
server and ensure that the following line is active (no leading '#'= ):

X2GO_NXAGENT_DEFAULT_OPTIONS+=3D" -extension GLX"

Then start a new session (with transient mark mode enabled) and retry.
Is that working better?

Uli


--
Yan
--0000000000006b3d50058454fb81--