I'm trying to run a remote X-session on a satellite link. The ping latency is typically 800ms. I have no trouble ssh'ing to the remote machine, but, whenever I try to connect a remote session via the x2goclient, it ends within a couple seconds with a dialog box saying:
Timeout connecting to raven
raven is the remote hostname.
Both machines are running Debian Jessie. The x2goclient is version 4.4.1.0
Is there some connection timeout parameter that I could increase to make it possible to use high latency links? Is this fixed in newer versions?
Thanks!
-- Brent Roman MBARI Software Engineer Tel: (831) 775-1808 7700 Sandholdt Road, Moss Landing, CA 95039 mailto:brent@mbari.org http://www.mbari.org/~brent
Am 12.03.2018 um 20:28 schrieb Brent Roman:
I'm trying to run a remote X-session on a satellite link. The ping latency is typically 800ms.
[...]
Is there some connection timeout parameter that I could increase to make it possible to use high latency links? Is this fixed in newer versions?
Brent, there currently is no such option in the GUI.
Seeing as you posted from your employer's E-Mail address, may I suggest you ask your employer if they might want to sponsor researching whether or not X2Go can be made to work over high-latency links, and adding a timeout/keepalive feature to the GUI, if it turns out to be possible?
<shameless plug> X2Go also has a commercial side, where various companies - including my own - offer support contracts with guaranteed response times as well as consultancy and paid-for development work if someone wants to see a bug fixed or a new feature added in a certain time frame. What makes my company special is, IMHO:
- I'm the current X2Go Project/Community Coordinator, so the development lead and the developers tend to listen to me.
- As far as I know, we are the only company providing X2Go support that isn't a one-man-show. Oh, and we already have US customers.
- We sub-contract other developers from the X2Go community on demand, so you only have one person you need to talk to - me - and you will only receive one invoice, even if the task involved several freelance or part-time X2Go developers.
Our hourly rate for consultancy work and fixing issues outside of a support contract is 125 EUR. With a support contract, you get guaranteed response times and lower hourly rates if you buy a certain amount of hours in advance. </shameless plug>
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
After updating to Debian Stretch, I see the following error when starting a new desktop XFCE session:
(xfsettingsd:11973): xfsettingsd-CRITICAL **: Your XI is too old (1.3) version 1.4 is required.
I'm guessing this means that the emulation of xinput X2Go provides is for version 1.3, but XFCE 4.12 requires xinput >= 1.4 Is this correct?
The session starts and is usable, but it locks the screen every 20 seconds. I run lightdm with a 20 second DPMS timeout. Normally, the DPMS timeout is increased to 600 seconds when the session starts, but...
xset -q reports:
DPMS (Energy Star): Display is not capable of DPMS
It seems that I cannot change the underlying Xserver's DPMS parameters.
Is this related to the XI too old error above?
Can anyone recommend a workaround until 3.60 is released with support for xinput 1.4?
Thanks in Advance,
-- Brent Roman MBARI Software Engineer Tel: (831) 775-1808 7700 Sandholdt Road Moss Landing, CA 95039 mailto:brent@mbari.org http://www.mbari.org/~brent
-
Brent Roman -
Stefan Baur