Hello list,
I have run x2go for many years now without any problem. I have two different servers running Debian testing and x2go 4.1.0.3-5, multiple clients running the same OS and x2go client. I run WindowMaker both on client and servers. This has worked for many years.
Weird thing: the active clicking point for the mouse is 1 cm above the mouse. Restarting client and server does not make any difference. AFAIK these x2go versions have not changed (underlying libraries might have of course). I tested this on a few clients: same problem. It make x2go almost unusable.
Anyone a hint what to test and where to look for this weird issue?
R.
-- richard lucassen http://contact.xaq.nl/
On Sun, 13 Dec 2020 16:41:30 +0100 richard lucassen <mailinglists@lucassen.org> wrote:
I have run x2go for many years now without any problem. I have two different servers running Debian testing and x2go 4.1.0.3-5, multiple clients running the same OS and x2go client. I run WindowMaker both on client and servers. This has worked for many years.
Weird thing: the active clicking point for the mouse is 1 cm above the mouse. Restarting client and server does not make any difference. AFAIK these x2go versions have not changed (underlying libraries might have of course). I tested this on a few clients: same problem. It make x2go almost unusable.
Apparently this only occurs in fullscreen mode. It looks like the mouse is behaving as if there were a topbar (which is not the case in fullscreen mode)
Any thoughts?
R.
-- richard lucassen http://contact.xaq.nl/
On Sun, 13 Dec 2020 16:41:30 +0100 richard lucassen <mailinglists@lucassen.org> wrote:
I have run x2go for many years now without any problem. I have two different servers running Debian testing and x2go 4.1.0.3-5, multiple clients running the same OS and x2go client. I run WindowMaker both on client and servers. This has worked for many years.
Weird thing: the active clicking point for the mouse is 1 cm above the mouse. Restarting client and server does not make any difference. AFAIK these x2go versions have not changed (underlying libraries might have of course). I tested this on a few clients: same problem. It make x2go almost unusable.
An Apple client has the same problem.
-- richard lucassen http://contact.xaq.nl/
Can you please check if this is dependent on the client side window manager? Please also report the version of nxagent on the server.
Uli
richard lucassen <mailinglists@lucassen.org> schrieb am Do., 17. Dez. 2020, 11:17:
On Sun, 13 Dec 2020 16:41:30 +0100 richard lucassen <mailinglists@lucassen.org> wrote:
I have run x2go for many years now without any problem. I have two different servers running Debian testing and x2go 4.1.0.3-5, multiple clients running the same OS and x2go client. I run WindowMaker both on client and servers. This has worked for many years.
Weird thing: the active clicking point for the mouse is 1 cm above the mouse. Restarting client and server does not make any difference. AFAIK these x2go versions have not changed (underlying libraries might have of course). I tested this on a few clients: same problem. It make x2go almost unusable.
An Apple client has the same problem.
-- richard lucassen http://contact.xaq.nl/
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Thu, 17 Dec 2020 11:25:10 +0100 Ulrich Sibiller <uli42@gmx.de> wrote:
Can you please check if this is dependent on the client side window manager? Please also report the version of nxagent on the server.
I asked someone with an Apple to test it and I asked him to also test a windows version. Well, the Apple shows this issue but the Windows version seems to work well:
Windows client (both on 4k and 1920x1366 screen): 4.1.2.2 Qt: 4.8.6
Apple client: version 4.1.2.2 (QT 4.8.7)
Linux Debian Bullseye client: x2goclient 4.1.2.2-2 amd64 (Qt5) nxproxy 2:3.5.99.25-1 amd64
Client: custom desktop "/usr/bin/ssh-agent /usr/bin/wmaker"
Linux Debian Bullseye server: nxagent 2:3.5.99.25-1 amd64 x2goserver 4.1.0.3-5 amd64 x2goserver-common 4.1.0.3-5 amd64 x2goserver-x2goagent 4.1.0.3-5 amd64 x2goserver-xsession 4.1.0.3-5 amd64 x2goserver-extensions 4.1.0.3-5 amd64
As far as I remember there have been no x2go updates in the last two months. A "zgrep x2go /var/log/dpkg.log*" shows last update was:
Server: x2go: 2020-02-19 nxagent: 2020-11-10
Linux client: x2goclient: 2020-03-21 nxproxy: 2020-11-10
As reported, this ONLY occurs in fullscreen mode.
-- richard lucassen http://contact.xaq.nl/
On Thu, Dec 17, 2020 at 12:04 PM richard lucassen <mailinglists@lucassen.org> wrote:
On Thu, 17 Dec 2020 11:25:10 +0100 Ulrich Sibiller <uli42@gmx.de> wrote:
Can you please check if this is dependent on the client side window manager? Please also report the version of nxagent on the server.
I asked someone with an Apple to test it and I asked him to also test a windows version. Well, the Apple shows this issue but the Windows version seems to work well:
Windows client (both on 4k and 1920x1366 screen): 4.1.2.2 Qt: 4.8.6
Apple client: version 4.1.2.2 (QT 4.8.7)
Linux Debian Bullseye client: x2goclient 4.1.2.2-2 amd64 (Qt5) nxproxy 2:3.5.99.25-1 amd64
Client: custom desktop "/usr/bin/ssh-agent /usr/bin/wmaker"
Linux Debian Bullseye server: nxagent 2:3.5.99.25-1 amd64 x2goserver 4.1.0.3-5 amd64 x2goserver-common 4.1.0.3-5 amd64 x2goserver-x2goagent 4.1.0.3-5 amd64 x2goserver-xsession 4.1.0.3-5 amd64 x2goserver-extensions 4.1.0.3-5 amd64
As far as I remember there have been no x2go updates in the last two months. A "zgrep x2go /var/log/dpkg.log*" shows last update was:
Server: x2go: 2020-02-19 nxagent: 2020-11-10
Linux client: x2goclient: 2020-03-21 nxproxy: 2020-11-10
The versions you mentioned are all ok/uptodate.
As reported, this ONLY occurs in fullscreen mode.
Please change the window manager on the Linux client and retry. I suggest openbox.
Uli
On Thu, 17 Dec 2020 12:45:13 +0100 Ulrich Sibiller <uli42@gmx.de> wrote:
The versions you mentioned are all ok/uptodate.
As reported, this ONLY occurs in fullscreen mode.
Please change the window manager on the Linux client and retry. I suggest openbox.
I just tried a Mate environment on a Debian Buster, but same issue. I started OpenBox on the server: same issue.
BUT: I installed OpenBox on the client and connected to the x2go server, either starting openbox or wmaker and the problem gets much much worse: the mouse click point is about 12cm higher and some 4cm to the left. Completely unusable. Tried on two different computers (both Debian Bullseye)
The server runs sys-V btw.
-- richard lucassen http://contact.xaq.nl/
On Thu, 17 Dec 2020 13:41:12 +0100 richard lucassen <mailinglists@lucassen.org> wrote:
Tried a connection from a Debian Buster (systemd) in an OpenBox client environment: same issue: about 12cm's too high and a few cm's left. Completely unusable.
-- richard lucassen http://contact.xaq.nl/
Unfortunately we only test on Linux.... Do you also see this on a Linux server?
Please report the output of the following commands both inside the session and on the client (outside the session):
- xdpyinfo -ext XINERAMA
- xrandr
How do switch to fullscreen? There are two keyboard shortcuts: ctrl-alt-f and ctrl-al-shift-f. Does one or the other make a difference?
Are you using wayland on the client side?
Uli
On Thu, Dec 17, 2020 at 2:00 PM richard lucassen <mailinglists@lucassen.org> wrote:
On Thu, 17 Dec 2020 13:41:12 +0100 richard lucassen <mailinglists@lucassen.org> wrote:
Tried a connection from a Debian Buster (systemd) in an OpenBox client environment: same issue: about 12cm's too high and a few cm's left. Completely unusable.
-- richard lucassen http://contact.xaq.nl/
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Thu, 17 Dec 2020 16:05:04 +0100 Ulrich Sibiller <uli42@gmx.de> wrote:
Unfortunately we only test on Linux.... Do you also see this on a Linux server?
I tested 2 Linux servers (both sysV):
- windowmanager WindowMaker
- windowmanager OpenBox
And the following clients: Debian Buster (systemd) Mate Debian Buster (systemd) OpenBox Debian Bullseye (sysV) WindowMaker (3 different computers) Debian Bullseye (sysV) OpenBox (3 different computers)
Please report the output of the following commands both inside the session and on the client (outside the session):
- xdpyinfo -ext XINERAMA
- xrandr
http://tmp.xaq.nl/x2go/index.html
Server:
How do switch to fullscreen? There are two keyboard shortcuts: ctrl-alt-f and ctrl-al-shift-f. Does one or the other make a difference?
I set client to fullscreen. I never used these shortcuts (thnx!). Anyway, switching to non-fullscreen and back to fullscreen seems to resolve the issue!
Are you using wayland on the client side?
No, just xserver.org
R.
-- richard lucassen http://contact.xaq.nl/
On Thu, Dec 17, 2020 at 4:53 PM richard lucassen <mailinglists@lucassen.org> wrote:
On Thu, 17 Dec 2020 16:05:04 +0100 Ulrich Sibiller <uli42@gmx.de> wrote:
Unfortunately we only test on Linux.... Do you also see this on a Linux server?
I tested 2 Linux servers (both sysV):
- windowmanager WindowMaker
- windowmanager OpenBox
Sorry, I got that wrong, should not do too many things simultaneously.
And the following clients: Debian Buster (systemd) Mate Debian Buster (systemd) OpenBox Debian Bullseye (sysV) WindowMaker (3 different computers) Debian Bullseye (sysV) OpenBox (3 different computers)
Please report the output of the following commands both inside the session and on the client (outside the session):
- xdpyinfo -ext XINERAMA
- xrandr
Looks alright, but slight dpi difference.
How do switch to fullscreen? There are two keyboard shortcuts: ctrl-alt-f and ctrl-al-shift-f. Does one or the other make a difference?
I set client to fullscreen. I never used these shortcuts (thnx!). Anyway, switching to non-fullscreen and back to fullscreen seems to resolve the issue!
OK, then it looks like we have an issue with fullscreen on session creation. I need to test that myself (when I find time).
Quick test: I have a test machine with nxagent 3.5.99.23 where I cannot see that behaviour. Does this also happen when you only run an xterm in a fullscreen session?
Uli
On Thu, 17 Dec 2020 22:06:59 +0100 Ulrich Sibiller <uli42@gmx.de> wrote:
Sorry, I got that wrong, should not do too many things simultaneously.
Women seem to be able to ;-)
I set client to fullscreen. I never used these shortcuts (thnx!). Anyway, switching to non-fullscreen and back to fullscreen seems to resolve the issue!
OK, then it looks like we have an issue with fullscreen on session creation. I need to test that myself (when I find time).
Quick test: I have a test machine with nxagent 3.5.99.23 where I cannot see that behaviour. Does this also happen when you only run an xterm in a fullscreen session?
I will do these tests tomorrow. I'll report the results!
R.
-- richard lucassen http://contact.xaq.nl/
On Thu, 17 Dec 2020 22:06:59 +0100 Ulrich Sibiller <uli42@gmx.de> wrote:
Quick test: I have a test machine with nxagent 3.5.99.23 where I cannot see that behaviour. Does this also happen when you only run an xterm in a fullscreen session?
Yep. And a ctrl-alt-f ctrl-shift-alt-f sequence resolves it.
-- richard lucassen http://contact.xaq.nl/
Is this still happening with nxagent 3.5.99.26?
Uli
On Fri, Dec 18, 2020 at 10:53 AM richard lucassen <mailinglists@lucassen.org> wrote:
On Thu, 17 Dec 2020 22:06:59 +0100 Ulrich Sibiller <uli42@gmx.de> wrote:
Quick test: I have a test machine with nxagent 3.5.99.23 where I cannot see that behaviour. Does this also happen when you only run an xterm in a fullscreen session?
Yep. And a ctrl-alt-f ctrl-shift-alt-f sequence resolves it.
-- richard lucassen http://contact.xaq.nl/
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Thu, 1 Apr 2021 13:55:16 +0200 Ulrich Sibiller <uli42@gmx.de> wrote:
Is this still happening with nxagent 3.5.99.26?
I discovered a few weeks ago that the problem had disappeared, so it might have been solved with an "apt upgrate".
Sorry for late reply btw. Thnx!
R.
-- richard lucassen https://contact.xaq.nl/
Good to hear that!
Uli
richard lucassen <mailinglists@lucassen.org> schrieb am Sa., 17. Apr. 2021, 16:36:
On Thu, 1 Apr 2021 13:55:16 +0200 Ulrich Sibiller <uli42@gmx.de> wrote:
Is this still happening with nxagent 3.5.99.26?
I discovered a few weeks ago that the problem had disappeared, so it might have been solved with an "apt upgrate".
Sorry for late reply btw. Thnx!
R.
-- richard lucassen https://contact.xaq.nl/
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Sat, 17 Apr 2021 18:55:43 +0200 Ulrich Sibiller <uli42@gmx.de> wrote:
Good to hear that!
It works like a charm Uli!
-- richard lucassen https://contact.xaq.nl/
-
richard lucassen -
Ulrich Sibiller