PPS:

The last update made me experiment a bit more with it. I've noticed that depending on the workspace there are different results what the client will see.

First of all if the server displays nothing, client will see a terminal window open either way.
When I connect to the server while it is on the first workspace in XFCE and then start typing in the terminal I can see maybe the first 2-3 letters reflected. However it stops then and those letters seem to either loop or be stuck. I can still move the mouse and the server will respond to clicks.

Also systemctl status x2goserver reveals the following error AFTER the client has connected:

/usr/sbin/x2gocleansession[1730]: USER-50-........_stS1XSHADuserXSHADPP0_dp24: state file for this session does not exist: /tmp/ .x2go-user/C-user-50-...........

I hope this helps to identify what is wrong?

Cheers
Sebastian





On Fri, Feb 21, 2020 at 2:59 PM Sebastian Schneider <schneider.seb@gmail.com> wrote:
PS: This might be of interest as well.
Just noticed another strange behavior that is most likely related.

I've asked a colleague to try logging in from a windows machine. Fresh install of X2Go Client (windows).
While the connection gets established for a brief time he can't even get to any screen before he gets kicked out again straight away.

However when I tried connecting again straight after I suddenly get some random responses from my computer (client). The occasionally jump to another workspace (using XFCE) but it randomly starts jumping back and forth without the actual input then.

I've rebooted my client and reconnected and the same happened again. Random jumps / flickers.
Then I rebooted the server and that behavior was gone. Basically back to 0 response from then on.

So yeah, looks like some strange behaviour from the server side.


On Fri, Feb 21, 2020 at 2:07 PM Sebastian Schneider <schneider.seb@gmail.com> wrote:
Hi Uli,

Thanks again for the quick response.
You were absolutely right. I accidentally searched with the "e" flag before and only got explicit results (my bad).

On Server:
NXAGENT - Version 3.5.99.22

On Client:
nxproxy/bionic 2:3.5.99.16-1

Looks like the latest versions?

Let me know if you can think of anything.
Thanks again
Sebastian

On Fri, Feb 21, 2020 at 1:12 PM Ulrich Sibiller <uli42@gmx.de> wrote:
On Fri, Feb 21, 2020 at 12:14 PM Sebastian Schneider
<schneider.seb@gmail.com> wrote:
>
> Thanks for the reply Uli and sorry for the delay.
> I had no direct access to the server until today so I am only getting back now.
>
> To answer your question with as much detail:
>
> Server (Linux Arch)
> x2goserver 4.1.0.3-3
> https://www.archlinux.org/packages/extra/x86_64/x2goserver/
> x2godesktopsharing 3.1.1.3-1 (however this doesn't actually work properly)
> https://aur.archlinux.org/packages/x2godesktopsharing/
>
> Client (Linux Mint)
> x2goclient 4.1.1.1-2ubuntu0.18.04.1
> https://packages.ubuntu.com/bionic/x11/x2goclient
>
> I was somewhat confused about the "nxagent". It isn't installed on either machine.
> I had a read about it (http://manpages.ubuntu.com/manpages/bionic/man1/nxagent.1.html)
>
> It wasn't installed as a requirement when pulling the x2go packages on either machine and neither is it documented on X2Go or Arch for standard installation.
> This might be silly question but is that required to work?

Yes, nxagent is the heart of the whole thing. In the first link above
to the x2goserver Arch page you can see that it has nxagent as
dependency. I don't know arch, but in a standard x2go setup you have
an nxagent binary somewhere and a link called x2goagent that points to
that binary. Maybe arch is only providing an x2goagent binary, I don't
know. When you are running an x2go session you can see a process
called x2goagent. You can run that binary like this: x2goagent
-version Please do this and report the output.

Uli