Bug#1072: X2Go Client: top 24 pixels in fullscreen session do not respond to mouse clicks
Package: x2goclient Version: 4.0.5.1
I am trying to start a full screen X2Go session which 1. takes up the entire display, and 2. responds to my mouse clicks everywhere in the session, but cannot accomplish this with any combination of settings.
Client OS: Debian Jessie / 8 / Stable, GNOME 3 desktop environment Client X2Go Client: 4.0.5.1 and 4.0.3.1 Server OS: Xubuntu 16.04 LTS Server x2goserver version: 4.0.1.19 Server x2goserver-xsession version: 4.0.1.19
When I choose "fullscreen", I get different behavior intermittently:
The client spawns across the entire screen but the *top panel inside the X2Go session* does not respond to any mouse clicks. I suspect the panel in my GNOME session running the X2Go client (which occupies the same pixels behind the panel inside the X2Go session) is stealing mouse focus. My mouse pointer turns black instead of white when I hover over the top 24 pixels or so, inside the X2Go session.
The client spawns what I would call a "maximized window". The top of the screen is still consumed by the title bar of the X2Go window, and the panel of the enclosing GNOME session in which the X2Go client is running.
I have observed both cases 1 (most common) and 2 with X2Go Client 4.0.5.1, and only case 1 with X2Go client 4.0.3.1.
When I choose "Display 1" in the Input/Output settings, the X2Go session displays only in the upper-left quadrant of my display; the rest of the screen is black.
Thank you,
Chris Martin
Hi,
This is still a problem on Ubuntu 20.04 with X2Go Client 4.1.2.2 connecting to XFCE through x2goserver 4.1.0.4-0~1914~ubuntu16.04.1
If I put both my local gnome panel and the remote XFCE panel at the top, then the top pixels in remote desktop cannot be clicked (tool tips work).
If I put my local gnome panel to the left, then only the top left corner pixels of the remote top panel have the problem (which is where they intersect).
If I switch my local desktop environment to XFCE, no matter where I put the panels, it always work.
Cheers.
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".
Uli
On Tue, Feb 9, 2021 at 3:05 PM Sylvain Cuaz <sylvain@ilm-informatique.fr> wrote:
Le 09/02/2021 à 17:03, Ulrich Sibiller a écrit :
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_Gor...
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
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:
-
Chris Martin -
Sylvain Cuaz -
Ulrich Sibiller -
Ulrich Sibiller