<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 03/26/2018 03:53 PM, Mihai Moldovan
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1b5e967d-c99d-da0e-a425-19befca892b6@ionic.de">Please
make sure that nx-libs 3.5.99.16 is installed on the server side.
<br>
</blockquote>
<blockquote type="cite"
cite="mid:1b5e967d-c99d-da0e-a425-19befca892b6@ionic.de">This
sounds like a typical incarnation of the DPMS bug, fixed with
nx-libs 3.5.99.15.
</blockquote>
<br>
thanks Mihai<br>
<br>
<br>
I confirm that the server giving the first error, i.e. "<b
class="moz-txt-star">The remote proxy closed the connection while
negotiating<span class="moz-txt-tag"> ...</span></b>"<br>
has indeed installed an older version of libnx-x11 (3.5.0.33~710). <br>
<br>
after letting apt-get to upgrade the nx libraries and x2go packages,<br>
I saw the libnx-x11 was replaced by a new package named libnx-x11-6,
and<br>
the version is now 3.5.99.16. However, now I start seeing the 2nd
error<br>
message on those machines, i.e. "connection failed".<br>
<br>
<blockquote type="cite"
cite="mid:1b5e967d-c99d-da0e-a425-19befca892b6@ionic.de">
<pre wrap="">However, this doesn't sound like it. Normally the DPMS bug only manifests after
a pretty long time (say, an hour or 1.5h, depending on DPMS settings), but not
right away after starting the session. I haven't yet seen such an error message
yet. It's possible that it's caused by the session repositioning on non-first
displays/nxagent crashing bug as fixed with nx-libs 3.5.99.16, but normally that
incarnates differently (i.e., nxagent is being started successfully, but then
dies quickly while starting the session without a client-side error message).</pre>
</blockquote>
<br>
here is a dump of the session.log file under the failed session:<br>
<br>
<br>
<code>NXAGENT - Version 3.5.99.16</code><code><br>
</code><code><br>
</code><code>Copyright (c) 2001, 2011 NoMachine
(<a class="moz-txt-link-freetext" href="http://www.nomachine.com">http://www.nomachine.com</a>)</code><code><br>
</code><code>....</code><code><br>
</code><code>See <a class="moz-txt-link-freetext" href="https://github.com/ArcticaProject/nx-libs">https://github.com/ArcticaProject/nx-libs</a> for more
information.</code><code><br>
</code><code><br>
</code><code>Info: Agent running with pid '17844'.</code><code><br>
</code><code>Session: Starting session at 'Mon Mar 26 16:56:11
2018'.</code><code><br>
</code><code>Error: Aborting session with 'Unable to open display
'nx/nx,options=/tmp/.x2go-fangq/C-fangq-50-1522097770_stDXFCE_dp24/options:50''.</code><code><br>
</code><code>Session: Aborting session at 'Mon Mar 26 16:56:11
2018'.</code><code><br>
</code><code>Session: Session aborted at 'Mon Mar 26 16:56:11 2018'.</code><code><br>
</code><br>
<br>
<br>
strangely, the x2go window reports something differently, it says
(see attached screenshot)<br>
<br>
<code>"PANIC!" Failure negotiating the session in stage 7</code><code><br>
</code><code>...</code><code><br>
</code><code>Wrong version or invalid session authentication cookie.</code><code><br>
</code><code>....</code><code><br>
</code><br>
<br>
are these two error messages caused by a single issue or multiple?<br>
<br>
I've already restarted x2gosever, but no dice. any other files that
I need to reset/clear?<br>
<br>
thanks<br>
<br>
Qianqian<br>
<br>
<blockquote type="cite"
cite="mid:1b5e967d-c99d-da0e-a425-19befca892b6@ionic.de">
<pre wrap="">
Mihai
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>