[X2Go-User] x2go-user Digest, Vol 60, Issue 9
Nigra Truo
nigratruo at gmail.com
Mon Jun 3 05:35:23 CEST 2019
Hi Uli,
sorry for the long delay. Thank you so much for the research, yes, the
compression details that you mentioned and how to set the connection
speed makes complete sense. The tiling is something that i have
noticed. I have been able to reduce the bandwidth requirements very
much, it does not look pretty (which is to be expected) BUT it does
work.
I wonder how I could put this documentation on the x2go documentation
site, so it would be avialable to everybody. The idea would be that if
somebody looks for this, they can find it.
Thanks,
Markus
On Mon, Apr 29, 2019 at 2:28 PM <x2go-user-request at lists.x2go.org> wrote:
>
> Send x2go-user mailing list submissions to
> x2go-user at lists.x2go.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.x2go.org/listinfo/x2go-user
> or, via email, send a message with subject or body 'help' to
> x2go-user-request at lists.x2go.org
>
> You can reach the person managing the list at
> x2go-user-owner at lists.x2go.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of x2go-user digest..."
>
>
> Today's Topics:
>
> 1. x2goserver - Unable to open display (Matúš Bendžela)
> 2. Re: X2go Connection / compression Settings defunct?
> Documentation? (Tristan Miller)
> 3. Re: x2go-user Digest, Vol 60, Issue 8 (martti pitkanen)
> 4. Re: X2go Connection / compression Settings defunct?
> Documentation? (Ulrich Sibiller)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 29 Apr 2019 14:04:19 +0200 (CEST)
> From: Matúš Bendžela <m.bendzela at tutanota.com>
> To: <x2go-user at lists.x2go.org>
> Subject: [X2Go-User] x2goserver - Unable to open display
> Message-ID: <Ldcyo3V--3-1 at tutanota.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> I am unable to connect to the x2goserver. I have 3 almost same servers with Ubuntu 16.04, on two of them x2goserver is working, but on the third not. Version of the x2goserver packge is 4.1.0.3. I've tried all solutions I found. Here is the error message from the server (I replaced the IP address with X.X.X.X):
>
> #> cat session-C-mbendzela-59-1556531225_stDXFCE_dp24.log
>
> running as X2Go Agent
>
> running as X2Go Agent
>
> running as X2Go Agent
>
> running as X2Go Agent
>
> running as X2Go Agent
>
> running as X2Go Agent
>
> running as X2Go Agent
>
> running as X2Go Agent
>
> NXAGENT - Version 3.5.99.20
>
> Copyright (c) 2001, 2011 NoMachine (http://www.nomachine.com <http://www.nomachine.com>)
> Copyright (c) 2008-2014 Oleksandr Shneyder <o.shneyder at phoca-gmbh.de <mailto:o.shneyder at phoca-gmbh.de>>
> Copyright (c) 2011-2016 Mike Gabriel <mike.gabriel at das-netzwerkteam.de <mailto:mike.gabriel at das-netzwerkteam.de>>
> Copyright (c) 2014-2016 Ulrich Sibiller <uli42 at gmx.de <mailto:uli42 at gmx.de>>
> Copyright (c) 2014-2016 Mihai Moldovan <ionic at ionic.de <mailto:ionic at ionic.de>>
> Copyright (c) 2015-2016 Qindel Group (http://www.qindel.com <http://www.qindel.com>)
> See https://github.com/ArcticaProject/nx-libs <https://github.com/ArcticaProject/nx-libs> for more information.
>
> Info: Agent running with pid '1602'.
> Session: Starting session at 'Mon Apr 29 11:47:06 2019'.
> Info: Proxy running in client mode with pid '1602'.
> Info: Using errors file '/tmp/.x2go-mbendzela/session-C-mbendzela-59-1556531225_stDXFCE_dp24.log'.
> Info: Using stats file '/home/mbendzela/.x2go/C-mbendzela-59-1556531225_stDXFCE_dp24/C-mbendzela-59-1556531225_stDXFCE_dp24/stats'.
> Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
> Warning: Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
> Info: Waiting for connection from 'localhost' on socket 'tcp:*:30028'.
> Loop: WARNING! Refusing connection from 'X.X.X.X' on port '30028'.
> Warning: Refusing connection from 'X.X.X.X'.
> Loop: PANIC! Connection with remote host 'localhost' could not be established.
> Error: Connection with remote host 'localhost' could not be established.
> Error: Aborting session with 'Unable to open display 'nx/nx,options=/home/mbendzela/.x2go/C-mbendzela-59-1556531225_stDXFCE_dp24/options:59''.
> Session: Aborting session at 'Mon Apr 29 11:47:56 2019'.
> Session: Session aborted at 'Mon Apr 29 11:47:56 2019'.
>
>
> Here is the error message from the X2goclient:
>
> Loop: PANIC! The remote NX proxy closed the connection.
> Error: The remote NX proxy closed the connection.
> Loop: PANIC! Failure negotiating the session in stage '7'.
> Error: Failure negotiating the session in stage '7'.
> Loop: PANIC! Wrong version or invalid session authentication cookie.
> Error: Wrong version or invalid session authentication cookie.
> Session: Terminating session at 'Mon Apr 29 12:37:58 2019'.
> Session: Session terminated at 'Mon Apr 29 12:37:58 2019'.
>
>
> When I connect to the server trough ssh with the -AX parameters (ssh -AX X.X.X.X), run command "x2goagent :10 &!" and then I run "/bin/bash /usr/bin/x2goruncommand 10 $(pgrep x2goagent|head -1) test 45342 xfce4-session nosnd R", it will start.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.x2go.org/pipermail/x2go-user/attachments/20190429/3265f882/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 29 Apr 2019 15:28:01 +0200
> From: Tristan Miller <psychonaut at nothingisreal.com>
> To: x2go-user at lists.x2go.org
> Subject: Re: [X2Go-User] X2go Connection / compression Settings
> defunct? Documentation?
> Message-ID: <20190429152732.39904627.psychonaut at nothingisreal.com>
> Content-Type: text/plain; charset="utf-8"
>
> Dear Nigra,
>
> On Fri, 26 Apr 2019 18:48:34 -0700, Nigra Truo
> <nigratruo at gmail.com> wrote:
> > I'm forced to work with some extreme bandwith restrictions and was
> > looking into using more compression and/or the Modem / ISDN connection
> > setting. (I'm down to old time modem speeds, 128 kbit or less)
> > So far I could not find any documentation that shows what these really
> > do. I normally use the ADSL one, which works. The Modem and ISDN
> > setting seems broken (and has been for as long as I rememeber), they
> > don't really reduce the bandwidth usage nor improve latency.
> > When switching to Modem, the screen updates actually get much worse, I
> > can watch the system update the screen in lines (not the whole screen
> > is updated in one go), which looks like a bug.
> > I have had success setting the image quality to a lower setting, the
> > screen looks worse, which is a good indicator that it is working.
> > I can't find any documentation on what the difference is between
> > different compression methods. Can you point me in the right
> > direction?
> > If I can find the info, I would be up for updating the documentation
> > so that others can find it better.
>
> I asked pretty much the same question here in 2017. The only response
> I got was from another user who, like you and me, was only able to make
> a few observations by trial and error testing:
> <http://lists.x2go.org/pipermail/x2go-user/2017-February/004254.html>
>
> I agree that it would be nice to get a comprehensive overview of the
> different settings.
>
> Regards,
> Tristan
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Tristan Miller
> Free Software developer, ferret herder, logologist
> https://logological.org/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 833 bytes
> Desc: OpenPGP digital signature
> URL: <http://lists.x2go.org/pipermail/x2go-user/attachments/20190429/a13116aa/attachment-0001.sig>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 29 Apr 2019 21:01:03 +0300
> From: martti pitkanen <martti.pitkanen at aplcomp.fi>
> To: x2go-user at lists.x2go.org
> Subject: Re: [X2Go-User] x2go-user Digest, Vol 60, Issue 8
> Message-ID: <0b0a6631-4f2a-b2b2-9964-8d7b90bccbe8 at aplcomp.fi>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Hi All,
>
> This error msg has not reappeared since then.
> In the mean time, I updated the Ubuntu server.
> There seemed to be updates refering to nx-libs.
> I rebooted to the server.
>
> Thanks, Martti
>
>
> On 4/28/19 1:00 PM, x2go-user-request at lists.x2go.org wrote:
> > Send x2go-user mailing list submissions to
> > x2go-user at lists.x2go.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://lists.x2go.org/listinfo/x2go-user
> > or, via email, send a message with subject or body 'help' to
> > x2go-user-request at lists.x2go.org
> >
> > You can reach the person managing the list at
> > x2go-user-owner at lists.x2go.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of x2go-user digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: VcXsrv (Stefan Baur)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Sat, 27 Apr 2019 22:10:36 +0200
> > From: Stefan Baur <X2Go-ML-1 at baur-itcs.de>
> > To: x2go-user at lists.x2go.org
> > Subject: Re: [X2Go-User] VcXsrv
> > Message-ID: <06702841-5e84-a108-a598-a2f5857a8101 at baur-itcs.de>
> > Content-Type: text/plain; charset=utf-8
> >
> > Am 27.04.19 um 21:11 schrieb Ulrich Sibiller:
> >> Can you please translate the error message?
> > VcXsrv windows xserver (X2Go/arctica builds)
> > stopped working.
> > The problem interrupted the correct operation of the program. Windows
> > closes the program and tells you if there is a solution to the problem.
> >
> > [Close the program]
> >
> --
> --- Martti Pitkänen APLcomp Oy Mariankatu 17 00170 Helsinki Finland Tel
> +358 9 1357266 Mob +358 40 0602157 www.aplcomp.com Mail: P.O.BOX 126
> 00171 Helsinki Finland
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.x2go.org/pipermail/x2go-user/attachments/20190429/7fcb5a49/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 29 Apr 2019 23:19:07 +0200
> From: Ulrich Sibiller <uli42 at gmx.de>
> To: Tristan Miller <psychonaut at nothingisreal.com>
> Cc: x2go users <x2go-user at lists.x2go.org>
> Subject: Re: [X2Go-User] X2go Connection / compression Settings
> defunct? Documentation?
> Message-ID:
> <CANVnVY+X9YautssKSJHBkRG1RY909weDHiEUeV+BRx1T3c3KEA at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Mon, Apr 29, 2019 at 3:42 PM Tristan Miller
> <psychonaut at nothingisreal.com> wrote:
> >
> > Dear Nigra,
> >
> > On Fri, 26 Apr 2019 18:48:34 -0700, Nigra Truo
> > <nigratruo at gmail.com> wrote:
> > > I'm forced to work with some extreme bandwith restrictions and was
> > > looking into using more compression and/or the Modem / ISDN connection
> > > setting. (I'm down to old time modem speeds, 128 kbit or less)
> > > So far I could not find any documentation that shows what these really
> > > do. I normally use the ADSL one, which works. The Modem and ISDN
> > > setting seems broken (and has been for as long as I rememeber), they
> > > don't really reduce the bandwidth usage nor improve latency.
> > > When switching to Modem, the screen updates actually get much worse, I
> > > can watch the system update the screen in lines (not the whole screen
> > > is updated in one go), which looks like a bug.
> > > I have had success setting the image quality to a lower setting, the
> > > screen looks worse, which is a good indicator that it is working.
> > > I can't find any documentation on what the difference is between
> > > different compression methods. Can you point me in the right
> > > direction?
> > > If I can find the info, I would be up for updating the documentation
> > > so that others can find it better.
>
> The code sets tile size and defer parameters depending on the link
> speed, but you can also set these parameters on your own, see man
> nxagent:
>
> defer=<int>
> defer image updates (enabled for all connection types
> except LAN), accepts values 0, 1 and 2
>
> The default value can be set via the command line
> (-defer). The value provided as nx/nx option is set when resuming a
> session, thus it overrides the command line default.
>
> tile=<string>
> set the tile size in pixels (<W>x<H>) for bitmap data
> sent over the wire
>
> The default value can be set via the command line
> (-tile). The value provided as nx/nx option is set when resuming a
> session, thus it overrides the command line default.
>
> You can add the desired valued to the X2GO_NXOPTIONS= line in
> /etc/x2go/x2goagent.options, e.g. "menu=1,defer=2,tile=128x128"
>
> * Each defer level adds the following rules to the previous ones:
> *
> * Level 0 Eager encoding.
> *
> * Level 1 No data is put or copied on pixmaps, marking them always
> * as corrupted and synchronizing them on demand, i.e. when
> * a copy area to a window is requested, the source is syn-
> * chronized before copying it.
> *
> * Level 2 The put images over the windows are skipped marking the
> * destination as corrupted. The same happens for copy area
> * and composite operations, spreading the corrupted regions
> * of involved drawables.
>
> Here are the defaults as found in the code:
>
> case LINK_TYPE_MODEM:
> deferLevel = 2;
> tileWidth = 64;
> tileHeight = 64;
> case LINK_TYPE_ISDN:
> deferLevel = 2;
> tileWidth = 64;
> tileHeight = 64;
> case LINK_TYPE_ADSL:
> deferLevel = 2;
> tileWidth = 4096;
> tileHeight = 4096;
> case LINK_TYPE_WAN:
> deferLevel = 1;
> tileWidth = 4096;
> tileHeight = 4096;
> case LINK_TYPE_NONE:
> case LINK_TYPE_LAN:
> deferLevel = 0;
> tileWidth = 4096;
> tileHeight = 4096;
> default:
> deferLevel = 0;
> tileWidth = 64;
> tileHeight = 64;
>
> To my surprise I found another parameter today which is currently
> undocumented: -irlimit <kB/s>. This will limit the amount of data that
> is used to update drawables on the real display. It can only be passed
> via command line. To play with it add it to
> /etc/x2go/x2goagent.options.
>
> > I asked pretty much the same question here in 2017. The only response
> > I got was from another user who, like you and me, was only able to make
> > a few observations by trial and error testing:
> > <http://lists.x2go.org/pipermail/x2go-user/2017-February/004254.html>
> >
> > I agree that it would be nice to get a comprehensive overview of the
> > different settings.
>
> Well, I have done some research tonight:
>
> First it is worth noting that what we are talking about here is the
> way NX will compress images travelling the wire. NX also (delta)
> compresses the message format that X11 uses. This is unaffected by the
> pack method setting. So if you only have an xterm handling some text
> you probalby do not see much difference after changing the pack method
> because there are not many images involved. Also note that NX uses a
> cache so image compression will help in low bandwidth situations, but
> maybe less than expected. That's because once the image has travelled
> the wire it will be cached on the other side and not travel the wire
> again.
>
> x2goclient has three command line options that will influence the compression:
>
> --link Set default link type (modem,isdn,adsl,wan or lan, default: adsl).
>
> --pack Set default pack method (default: '16m-jpeg').
>
> --quality
> Set default image quality(0-9, default: 9).
>
> These can also be set in the Connection tab of the chosen session.
>
> The values you use for these parameter are passed down to the nx
> software. Some of the parameters there are described in "man nxproxy"
> as follows:
>
> link=<string>
> An indication of the link speed that is going to be
> used between the proxies. Usually the compression and the other link
> parameters depend on this setting. The value can be either 'modem',
> 'isdn', 'adsl', 'wan', 'lan', 'local' or a bandwidth
> specification, like for example '56k', '1m', '100m', etc.
> data=<int>
> Enable or disable the ZLIB data compression. It is
> possible to specify a value between 0 and 9. Usually the value is
> chosen automatically based on the requested link setting.
> stream=<int>
> Enable or disable the ZLIB stream compression. The
> value, between 0 and 9, is usually determined according to the
> requested link setting. Not fully implemented in nx-X11 Agent, yet.
> pack=<string>
> Determine the method used to compress images.
>
> Now, the pack and quality settings define the compression algorithm
> and the quality of the compressed images. In general there are several
> groups of compression methods. Most of them will use a user-provided
> number of colors from 8 to 16m. Generic form:
> <number-of-colors>[-<method>[-<quality>]]
> - none (no image compression, lossless)
> - masked (reduce number of bits per pixel, lossy): Format of the pack
> parameter: "<number of colors>", e.g "16m"
> - jpeg (jpeg compression, lossy): <number of colors>-jpeg, e.g. "16m-jpeg"
> - png (png compression, lossy): <number of colors>-png, e.g. "4k-png"
> - rgb (zlib compression with Z_DEFAULT_STRATEGY, lossless) : "rgb" or
> "16ḿ-rgb" /(16m is the only number of colors supported)
> - Run Length Encoding (zlib compression with Z_RLE strategy,
> lossless): "rle" or "16m-rle" (16m is the only number of colors
> supported)
> - bitmap (remove each 4th byte, lossless): "bitmap" or "16m-bitmap"
> (16m is the only number of colors supported)
>
> For the lossy compressors the string can also have a "-<quality>"
> suffix. This suffix will define the pack quality. The default is "9".
>
> There are some hig level compression modes, too, that will map to one
> from the list above:
> - "lossy" will map to "16m-jpeg"
> - "lossless" will map to "16m-rle-9" for link=lan and "16m-bitmap" for
> all other link types.
> - "adaptive" will choose lossy or lossless, depending on the
> characteristics of the image
>
> If no pack method is provided it will be set automatically from the
> link parameter:
> - modem: adaptive-3
> - isdn: adaptive-5
> - adsl: adaptive-7
> - wan: adaptive-9
> - lan: adaptive-9
>
> Images, that have a width or height of 2 or less pixels or are not
> bigger than 512 bytes will not be compressed (but they are still
> cached).
>
> Hope this helps,
>
> Uli
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> x2go-user mailing list
> x2go-user at lists.x2go.org
> https://lists.x2go.org/listinfo/x2go-user
>
> ------------------------------
>
> End of x2go-user Digest, Vol 60, Issue 9
> ****************************************
--
Por sperto kaj lerno ne sufiĉas eterno.
More information about the x2go-user
mailing list