On Mon, 29 Jan 2018 13:55:07 +0100
Gromit wrote:
> Had this same problem under Windows 10.
>
> Started x2goclient.debug --debug and it showed me that the
> permissions for the ssh_host_rsa_key are too open (0770).
>
> Installed cygwin to check these permissions under windows and the
> user- and
On Wed, 31 Jan 2018 10:33:22 +
Nicolas De Cock wrote:
> I get the following error message when starting X2Go client. Is there
> a way to fix it? I would like to exchange files from X2Go to my own
> computer.
You can try the workaround explained in #1156.
__
On Linux, the X2Go server stores the session files in /tmp/.x2go-* .
Now, whenever a coworker leaves for vacation, those files are not
getting updated and thus get deleted by tmpwatch on CentOS 6 or
systemd-tmpfiles on CentOS 7; when the coworker comes back and tries to
resume the session, it goes
Package: x2goserver
Version: 4.0.1.0
I put this in the x2goserver section but I'm not quite sure if it's the
right component that suffers from this issue.
In my company, we recently began to experience an issue similar to the
one reported in archived bug #673 [1] and on the X2Go-User list [2]
bac
On Wed, 14 Nov 2018 21:50:59 +0100
Ulrich Sibiller wrote:
> That has been implemented on purpose by nomachine to take some load
> off the server. You can disable that via the sleep option:
>sleep=
> delay X server operations when suspended (provided in
> msec), set to 0 to k
On Fri, 16 Nov 2018 09:54:51 +0100
Ulrich Sibiller wrote:
> In my tests I have changed the _first_ entry in the options file, the
> one without the +. Does that make any difference for you?
It does not make any difference about the session suspension issue if I
either set "-options" alone (witho