X2Go Bug report logs - #1072
X2Go Client: top 24 pixels in fullscreen session do not respond to mouse clicks

version graph

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

Reported by: Chris Martin <cmart.cyverse@gmail.com>

Date: Sat, 13 Aug 2016 03:30:02 UTC

Severity: normal

Found in version 4.0.5.1

Full log


🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#1072: [X2Go-Dev] Bug#1072: Bug#1072: X2Go Client: top 24 pixels in fullscreen session do not respond to mouse clicks
Reply-To: Ulrich Sibiller <uli42@gmx.de>, 1072@bugs.x2go.org
Resent-From: Ulrich Sibiller <uli42@gmx.de>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Tue, 09 Feb 2021 16:55:02 +0000
Resent-Message-ID: <handler.1072.B1072.161288947817849@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 1072
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
References: <CAKsO3SX4Tz_PpHy97EgkOqWJRn7JT9bGkMy6tj4brObz2muyeg@mail.gmail.com> <b247ede2-ee93-911f-2f34-76348ca8607c@ilm-informatique.fr> <CANVnVYLs+t14wbLMoEwr6QDXhmDppjLXSx9UPwVKZ5naotCS8w@mail.gmail.com> <7bb4a85d-08c6-3c54-af4b-01c9009368fd@ilm-informatique.fr> <CAKsO3SX4Tz_PpHy97EgkOqWJRn7JT9bGkMy6tj4brObz2muyeg@mail.gmail.com>
Received: via spool by 1072-submit@bugs.x2go.org id=B1072.161288947817849
          (code B ref 1072); Tue, 09 Feb 2021 16:55:02 +0000
Received: (at 1072) by bugs.x2go.org; 9 Feb 2021 16: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,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,URIBL_BLOCKED
	autolearn=ham autolearn_force=no version=3.4.2
Received: from mail-yb1-f181.google.com (mail-yb1-f181.google.com [209.85.219.181])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 023985DACE
	for <1072@bugs.x2go.org>; Tue,  9 Feb 2021 17:51:12 +0100 (CET)
Received: by mail-yb1-f181.google.com with SMTP id 133so6137905ybd.5
        for <1072@bugs.x2go.org>; Tue, 09 Feb 2021 08:51:12 -0800 (PST)
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=xOMUFd+/D9bOhwaGNnfJTg0HC/YOJDi7Ame/Qq9uWm0=;
        b=qxoGxzcaq4/QvEbaWLZD5TlY+bUJU7YWwzYocC0523mbcxj9DmaStfB+DbK0IGSdE0
         VYSGVM8tfwQMTiJT7THguv43x/C6Bv144/XcKDH19swHy2Ql6Va3iL1rcTQY8+LvEX0d
         Ux9gKpdD4AkacS7RCScYNbNd5/LEwAEZPfd1pVbeFP8H0NGiFCk4dOmJ3+YAi5I87WV/
         PLJfkhMB675JCEy8xs0FOZFv9Eqb6YJ2dSh9iHudyZTc3qhpq0zg7+b9J7APoMvg2uAH
         GVzvbq/zmaZESBoG8SKgIDW6JeRQBkzI+6kpkbhzrmDwUVXZyI6dsIsaYbog3dUnY0xG
         MJjg==
X-Gm-Message-State: AOAM533qZjfy9q+ymiqnV6rPU5Y9vCKOD7OwQKkAuXP6o0y2g/gXd6Eh
	6g3NMD7UZDEt8N4e/hrGvD2P/utteKAA0cPApIQPgnZA
X-Google-Smtp-Source: ABdhPJyxu7T1W1EYpxQgCQf5VhGHdCFiQW9ev7+iZopSUcmMyMIM1gOLloW3RZtDZN8VXV/zo/WlT5+bbFKhyboK4UM=
X-Received: by 2002:a25:3085:: with SMTP id w127mr23506326ybw.183.1612889471712;
 Tue, 09 Feb 2021 08:51:11 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <7bb4a85d-08c6-3c54-af4b-01c9009368fd@ilm-informatique.fr>
From: Ulrich Sibiller <uli42@gmx.de>
Date: Tue, 9 Feb 2021 17:50:59 +0100
Message-ID: <CANVnVYJ4HE0qoatL-EdJ87riRS2Dg4YpC4orFgkkUOmUmO7-aA@mail.gmail.com>
To: Sylvain Cuaz <sylvain@ilm-informatique.fr>
Cc: 1072@bugs.x2go.org
Content-Type: multipart/alternative; boundary="0000000000000602c505baea18ac"
[Message part 1 (text/plain, inline)]
How are you switching to fullscreen? In the default keyboard configuration
there's ctrl+alt+f and ctrl+alt+Shift+f. Can you please check if that
problem show with both. Also note the nxagent 3.5-99.25 is buggy regarding
full screen, so maybe you should try updating tie the freshly released
3.5.99.26.

Uli

Sylvain Cuaz <sylvain@ilm-informatique.fr> schrieb am Di., 9. Feb. 2021,
17:31:

> Le 09/02/2021 à 17:03, Ulrich Sibiller a écrit :
> > can you please post a screenshot of that situation where it does not
> > work? I don't really get what you mean by "If I put both my local
> > gnome panel and the remote XFCE panel at the top".
>
> I mean on my local session (where I launch x2go client), I have a gnome
> panel at the top of my
> screen (the default)
>
>
> https://simple.wikipedia.org/wiki/Ubuntu#/media/File:Ubuntu_20.10_Groovy_Gorilla_Desktop.png
>
> Then I launch x2go client and switch to full screen.
>
> https://i.stack.imgur.com/jaK2z.png
>
> The top pixels in the remote session inside x2go cannot be interacted
> with. Presumably because even
> though I can't see any pixels of my local gnome session, the clicks inside
> x2go aren't grabbed by
> x2go but rather by my local session. I.e. I cannot click on the
> application menu nor switch windows
> using the top panel. This a full screen bug, in windowed mode, the remote
> XFCE panel can be clicked.
>
>
> If on the other hand there's no gnome panel underneath the full screen
> x2go (e.g. my local gnome
> panel is on my right screen, my remote XFCE panel is on the left screen)
> then I can interact fine.
>
> Or I as said if my local desktop environment is XFCE then it always work
> no matter where are any panels.
>
> HTH
>
>
[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Wed Dec 11 22:04:05 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.