- x2go-user - X2Go ListServ

keyboard config on wayland
by Neal Becker 22 Jun '20

22 Jun '20

Both client and server are Fedora (31 and 32). I'm running a kde/wayland client, with capslock mapped to ctrl. When I connect to the server (running mate) everything works fine, except I don't have capslock mapped to ctrl. Every time I connect (not every time the session starts) I have to run setxkbmap -option caps:ctrl_modifier Oh actually one thing doesn't work. Cut/paste is totally nonfunctional. -- *Those who don't understand recursion are doomed to repeat it*

3 10

Problems using HTML5 kvm console
by Simon Beißer 20 Jun '20

20 Jun '20

Hello everyone, we use x2go in our company and it works really well. However, currently we have noticed two problems that occur in connection with an HTML5 KVM (remote console) client. Maybe one of you has an idea about these issues. 1st question When using the keyboard within the KVM console, we noticed that the arrow down key is incorrectly assigned and triggers an Enter. With the help of a keycode event tool I found that the NumpadEnter is transmitted there, see screenshot in the appendix. It seems that the wrong physical key (key code) is transmitted via x2go/nx. This has nothing directly to do with the keyboard layout used and therefore unfortunately cannot be changed within the virtual console. Is this error known? Is there a fix for it? 2nd question OpenGL/GLX is required for the KVM console. Unfortunately, only GLX1.2 is in use among the current nx-libs, which is why this does not work in Firefox. I have found only VirtualGL as workaround. Do you know other methods to make such applications running? Best regards Simon

3 6

Minor Enhancement Request
by Matt Rhodes 19 Jun '20

19 Jun '20

Hi, Short version, we'd like the ~/.ssh/config file to be respected for X2GoClient on Windows. Use case: I've been using X2Go heavily with some colleagues on Windows 10. We also use Git quite a bit, which provides SSH via repackaged MSYS. We frequently use the config file at ~/.ssh/config in order to set up all the hosts and connections we use, as there are a lot to manage. We connect a lot to various machines, including local VMs in Hyper-V using both SSH through Git Bash, as well as with X2Go Client. Pain: The current X2Go Client makes us maintain the configurations for each connection separately from the SSH Config file we already maintain. VM images complicate things as the IPs change on us more than we'd like and exacerbate the pain as we have to make IP updates in more than one location. Any useful workaround suggestions until X2Go client can be made to honor the ~/.ssh/config file? Matt.

2 1

OT: key modifiers
by Neal Becker 19 Jun '20

19 Jun '20

I have a nasty problem not related to x2go. My desktop is Fedora 32/KDE (pretty sure doesn't matter if wayland or x11). Sometimes I need to edit a MS office document. I've been using vmware horizon to connect to my work, and fire up powerpoint. After using this, (and after closing down horizon), I find all my modifier keys are gone, ALT, CTRL no longer do anything. I don't know how to recover without logoff/logon. As you can imagine, this is not really acceptable. Anyone know how to fix this? Thanks, Neal -- *Those who don't understand recursion are doomed to repeat it*

2 2

Can't start a plasma session
by Mihai Dobrescu 18 Jun '20

18 Jun '20

Hello, my x2go, provided by Sabayon Linux, can't start a KDE session because there is no more startkde command, I guess now it must run startplasma-wayland or startplasma-x11. Is there a version that implements that? Which one? Regards, Mihai Sorin Dobrescu

2 1

X2go session broker configuration question
by Simon Gao 18 Jun '20

18 Jun '20

Hi All, I'm trying to set up x2go session broker and following this instruction at wiki:advanced:x2gobroker:loadbalancing [X2Go - everywhere@home]. | | | | | | | | | | | wiki:advanced:x2gobroker:loadbalancing [X2Go - everywhere@home] | | | I'm running into an issue with:sudo x2gobroker-pubkeyauthorizer --broker-url http(s)://<broker-server>:<port>/<basepath>/pubkeys/ What files should I put in /pubkeys/ directory? When I put in one pub key for the session broker, I received following error: 2020-06-09 10:52:39,836 - broker - INFO - Authorizing access to this X2Go server for X2Go Session Broker 2020-06-09 10:52:39,836 - broker - INFO - at URL https://x2gobroker.example.com/pubkeys/x2gobrokerpubkey.pub 2020-06-09 10:52:39,866 - broker - INFO - Found 1 public key at URL https://x2gobroker.example.com/pubkeys/x2gobrokerpubkey.pub Traceback (most recent call last): File "/usr/sbin/x2gobroker-pubkeyauthorizer", line 206, in <module> keytype, pubkey, owner = new_pubkey.rsplit(" ", 2) ValueError: not enough values to unpack (expected 3, got 2) Any help is appreciated. Simon

2 2

Re: [X2Go-User] Matlab graphics performance when running in x2go
by Johannes Töger 18 Jun '20

18 Jun '20

I finally figured it out! Now I can run Matlab R2019b on Ubuntu 18.04 LTS with decent graphics performance over x2go, even with transparency using the Mesa llvmpipe software OpenGL driver. Benchmark for a simple scene: No transparency: ~40 ms per frame With transparency: ~58 ms per frmae So still some performance penalty for transparency, but much better. HOWTO: First install LLVM: sudo apt install llvm-dev I downloaded mesa-20.1.0 (latest version right now) and configured it like this (in the unzipped source directory): mkdir build cd build meson -D glx=gallium-xlib -D gallium-drivers=swrast -D platforms=x11 -D dri3=false -D dri-drivers="" -D vulkan-drivers="" -D buildtype=release -D optimization=3 -Dprefix=/usr/local/mesa-20.1.0/ Then I built and installed it as follows: ninja sudo ninja install Then to make Matlab load the new driver, I needed to modify Matlab's lib search path: cp $MATLAB_DIRECTORY/bin/.matlab7rc.sh ~ Edit the file ~/.matlab7rc.sh, find the glnxa* section and add /usr/local/mesa-20.1.0/lib/x86_64-linux-gnu to LDPATH_PREFIX Add to your .profile: export MESA_GL_VERSION_OVERRIDE=3.0 Seems like anything will work for the version override except for 3.1, but I didn't debug this further. — Johannes Töger Associate Senior Lecturer Cardiac MR Group Department of Clinical Sciences Lund, Clinical Physiology Lund University, Sweden -----Original Message----- From: Ulrich Sibiller <uli42(a)gmx.de> Sent: Wednesday, May 27, 2020 14:29 To: Johannes Töger <johannes.toger(a)med.lu.se> Subject: Re: [X2Go-User] Matlab graphics performance when running in x2go Thanks! On Wed, May 27, 2020 at 1:59 PM Johannes Töger <johannes.toger(a)med.lu.se> wrote: > > OK I see - we only have CUDA cards in those machines to do computations, so VirtualGL won't work then. > > Maybe I'll try to compile an optimized software Mesa/Gallium -- I'll let you know what happens if I find something interesting, so it's documented on the mailing list at least. > > > — > Johannes Töger > > Associate Senior Lecturer > Cardiac MR Group > Department of Clinical Sciences Lund, Clinical Physiology Lund > University, Sweden > > -----Original Message----- > From: Ulrich Sibiller <uli42(a)gmx.de> > Sent: Wednesday, May 27, 2020 13:20 > To: Johannes Töger <johannes.toger(a)med.lu.se> > Cc: x2go users <x2go-user(a)lists.x2go.org> > Subject: Re: [X2Go-User] Matlab graphics performance when running in > x2go > > On Wed, May 27, 2020 at 1:07 PM Johannes Töger <johannes.toger(a)med.lu.se> wrote: > > > > Thanks for your quick reply. > > > > It turns out that Matlab by default uses an older Mesa software rendering module (17.3) when there is no hardware OpenGL. I tried to compile my own version with additional optimizations and LLVMPipe etc, but Matlab wouldn't accept it. No more time to debug it today, but maybe later. > > > > Is there any documentation on using VirtualGL with x2go? I tried to google it, but no luck. > > Not that I am aware. I have never checked it out practically. > Generally you will have to dedicate the graphics hardware to that > (only) session which might make it a no-go, depending on your setup. > > Uli

3 6

Suspending sessions causes performance slowing down
by h i 17 Jun '20

17 Jun '20

Hello, We've been using x2go for a few months. Recent converts from using the old freenx nomachine 3.5. We installed x2goserver on Ubuntu mate 18.04 and have several users connecting through x2goclient 4.1.2.2 I have a question regarding suspended sessions with x2go. When we suspended an open session, we noticed the session stopped running. After resuming the session the next day, the process resumed executing. Thought this was strange and rebooted the server. Ran a few tests and noticed performance slows after suspending a session. Here is output from gxlgears. You can see the FPS decreases when the session suspends. The FPS returns back to normal (633 at the bottom), upon resuming the session. [cid:d252b9bd-2ad8-4a2a-800c-7e6c2a417eef] I searched online and discovered you can change the /etc/x2go/x2goagent.options to X2GO_NXOPTIONS="sleep=0". When doing this, now the performance increases considerably after suspending the session (middle portion of the output). [cid:4ba36847-76fc-4d46-ad13-1f0165a293c2] Is there a way to suspend an x2go session, and have no decrease or increase in performance? Is there some setting we can change to keep things running as is while session is suspended? Thanks in advance. h

3 12

Re: [X2Go-User] how to select single display
by Ulrich Sibiller 17 Jun '20

17 Jun '20

On Wed, May 27, 2020 at 5:25 PM gian sisal <giansisal19(a)gmail.com> wrote: > > Hi Ulrich,I try to explain it with a picture.. In attach you can see: my x2go Client (windows, ver 4.1.2.0 ... I think it's the latest one) connected to a remote system with 4 physical monitors. The point is: I would like to select "remote monitor #1" (or #2 or #3 or #4) to see it properly .I hope I was clear this time. Yes, thanks. So you are connecting to an existing desktop, a so-called shadow session. There's no option to restrict to only one monitor, you can only connect to whole desktop, that means all 4 monitors together. If your local screen is smaller that the remote desktop your will see the zoomed version which is barely usable. The only thing I can think of is enabling the viewport-mode by pressing ctrl-alt-r and then move to the monitors usign ctrl-alt-left/right/up/down (see /etc/x2go/keystrokes.cfg). Does that help? Uli

2 9

Blender 2.83 crashes
by Shoe Off Head 08 Jun '20

08 Jun '20

Hi, I have a legitimate need to use Blender (not a render farm) remotely for short/light work. I tested X2Go but only Blender 2.79 in the softwaregl mode did run (uses llvm-pipe for OpenGL software rendering). Blender 2.79 in normal mode and Blender 2.83 did crash in normal and softwareql mode. I wonder is real OpenGL (not software OpenGL like llvm-pipe) a No-Go for X2Go? Thanks for your help! P.S.: here is the Blender crash message: # backtrace ./blender(BLI_system_backtrace+0x1d) [0x6989e9d] ./blender() [0xc1548f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7f601308ef20] ./blender(_Z33GHOST_X11_ApplicationErrorHandlerP9_XDisplayP11XErrorEvent+0x11) [0x17304f1] /usr/lib/x86_64-linux-gnu/libX11.so.6(_XError+0x11a) [0x7f60142d18fa] /usr/lib/x86_64-linux-gnu/libX11.so.6(+0x3d82b) [0x7f60142ce82b] /usr/lib/x86_64-linux-gnu/libX11.so.6(+0x3d8d5) [0x7f60142ce8d5] /usr/lib/x86_64-linux-gnu/libX11.so.6(_XReply+0x240) [0x7f60142cf830] /usr/lib/x86_64-linux-gnu/libXi.so.6(XListInputDevices+0x84) [0x7f6014086d44] ./blender(_ZN15GHOST_SystemX1120refreshXInputDevicesEv+0x5f) [0x1731a3f] ./blender(_ZN15GHOST_SystemX11C1Ev+0x453) [0x1732193] ./blender(_ZN13GHOST_ISystem12createSystemEv+0x35) [0x172eda5] ./blender(GHOST_CreateSystem+0x9) [0x172dc29] ./blender(wm_ghost_init+0x2d) [0xee800d] ./blender(WM_init+0x275) [0xed4135] ./blender(main+0x2a3) [0xb4bf53] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f6013071b97] ./blender() [0xc11c0c]

2 2

Where are x2go compression options explained?
by Anton Driesse 29 May '20

29 May '20

X2Go offers a long list of compression options, obviously with some system behind them. Can anyone tell me where can I find explanations for these? Many thanks! Anton

2 4

how to select single display
by gian sisal 27 May '20

27 May '20

Hi everyone, I already asked about this topic, but no answers until now. So I'm going to ask again: I need to connect to a multi-monitor remote system (CentOS on it), I'm using a windows x2go client: no problems about connection: I'm able to connect to such remote system, but I need to select a single display I want to view on my screen. The actual 4.1.2.0 client version doesn't allow me to do this. Is there any update about this situation? Thanks in advance. Greetings. G

2 1

Re: [X2Go-User] X2Go Kdrive, current status? Ready for official release?
by Mike Gabriel 27 May '20

27 May '20

Hi Alex, hi all, On Mi 27 Mai 2020 11:55:46 CEST, Oleksandr Shneyder wrote: > Am 26.05.20 um 13:45 schrieb Mike Gabriel: >> Hi Alex, >> >> I wonder when would be a good point to get X2Go Kdrive to the majority >> of X2Go users. I will plan some X2Go work for July and this would be a >> good occasion to get a new X2Go Server version out containing the X2Go >> Kdrive wrapper code. >> >> What's the maturity status of X2Go Kdrive? Is it releasable? >> >> If not, we should get an X2Go server release out anyway and make sure it >> behaves well, if no X2Go Kdrive Xserver ist installed server-side. > Hi Mike, > I can't answer this question. My customers are using it productively > since longer than one year, however the number of use cases is limited > here. I didn't see a lot of test reports from other users. So I'm not > able (and don't want to) decide when it's ready for community release. > Maybe some of users, if anyone already tried it, can give some comments > on it. >> >> What do people think about this? @X2Go Users / Devs: what do others thing about the state of X2Go KDrive? Shall we open it up to a wider "audience"? Greets, Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de

1 0

Matlab graphics performance when running in x2go
by Johannes Töger 27 May '20

27 May '20

Hi everyone, We're running x2go on a compute server. Some of our apps are written in Matlab with interactive GUI:s. We are seeing quite poor graphics performance after moving from Matlab R2014a to R2019a, especially when using transparency in 3D graphics. This might be connected to the fact that Matlab goes into a software OpenGL mode. Does anyone have experience with this? Any solutions? Ubuntu 18.04 LTS MATE desktop environment Matlab R2019a x2goserver 4.1.0.3-0~1708~ubuntu1 libnx-x11-6:amd64 2:3.5.99.22-0+git20190 nxagent 2:3.5.99.22-0+git20190 - Johannes Töger Associate Senior Lecturer Cardiac MR Group Department of Clinical Sciences Lund, Clinical Physiology Lund University, Sweden

2 3

ICE default IO error handler doing an exit(), pid = xxxxxx, errno = 32, Fedora 32
by Robert Kudyba 26 May '20

26 May '20

Pardon the cross post from x2go dev list perhaps someone as seen this. Only affecting 1 workstation. On Fedora 32 with both MATE and XFCE, X2Go immediately quits with > Connection failed. This stackexchange question > <https://unix.stackexchange.com/questions/467507/x2go-unable-to-find-free-di…> suggests > running x2godbadmin --createdb but that doesn't help. > > x2goagent-4.1.0.3-6.fc32.x86_64 > x2goserver-xsession-4.1.0.3-6.fc32.noarch > x2goserver-common-4.1.0.3-6.fc32.noarch > x2goserver-4.1.0.3-6.fc32.x86_64 > > Connection failed. > > /usr/lib64/x2go/x2gocheckport: line 131: > connect('dbname=/var/lib/x2go/x2go_sessions','',...): syntax error in > expression (error token is "('dbname=/var/lib/x2go/x2go_sessions','',...)") > Unable to find free display port or insert new session into database; > parameters: port (50), hostname (ourdomain) and session name (). > > May 26 07:35:33 ourhostname /usr/bin/x2gostartagent[95534]: no free > display number available, cannot start new session. Retrying (run 10). > May 26 07:35:33 ourhostname /usr/bin/x2gostartagent[95535]: Unable to find > free display port or insert new session into database; parameters: port > (50), hostname (ourdomain) and session name (). > > cat .xsession-x2go-ourdomain.edu-errors > XSession-x2go: X session started for ouruser at Sun May 24 15:26:31 EDT > 2020 > ** Message: 15:26:33.626: couldn't access control socket: > /run/user/1200/keyring/control: No such file or directory > SSH_AUTH_SOCK=/run/user/1200/keyring/ssh > mate-session[141487]: WARNING: AT-SPI: Could not obtain desktop path or > name > > mate-session[141487]: WARNING: atk-bridge: GetRegisteredEvents returned > message with unknown signature > mate-session[141487]: WARNING: atk-bridge: get_device_events_reply: > unknown signature > mate-session[141487]: WARNING: atk-bridge: get_device_events_reply: > unknown signature > > ** (mate-settings-daemon:141818): WARNING **: 15:26:34.517: Could not open > RFKILL control device, please verify your installation > > ** (mate-panel:141832): WARNING **: 15:26:34.586: AT-SPI: Could not obtain > desktop path or name > > ** (mate-panel:141832): WARNING **: 15:26:34.608: atk-bridge: > GetRegisteredEvents returned message with unknown signature > > ** (mate-panel:141832): WARNING **: 15:26:34.608: atk-bridge: > get_device_events_reply: unknown signature > > ** (mate-panel:141832): WARNING **: 15:26:34.608: atk-bridge: > get_device_events_reply: unknown signature > > ** (mate-settings-daemon:141818): WARNING **: 15:26:35.152: AT-SPI: Could > not obtain desktop path or name > > > ** (mate-settings-daemon:141818): WARNING **: 15:26:35.154: atk-bridge: > GetRegisteredEvents returned message with unknown signature > > ** (mate-settings-daemon:141818): WARNING **: 15:26:35.154: atk-bridge: > get_device_events_reply: unknown signature > > ** (mate-settings-daemon:141818): WARNING **: 15:26:35.154: atk-bridge: > get_device_events_reply: unknown signature > SSH_AUTH_SOCK=/run/user/1200/keyring/ssh > vmware-user: could not open /proc/fs/vmblock/dev > SSH_AUTH_SOCK=/run/user/1200/keyring/ssh > SSH_AUTH_SOCK=/run/user/1200/keyring/ssh > > (caja:141846): Gtk-WARNING **: 15:26:36.752: Failed to register client: > GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register > client > Failure: Module initialization failed > > ** (polkit-mate-authentication-agent-1:141982): WARNING **: 15:26:36.825: > AT-SPI: Could not obtain desktop path or name > > > ** (polkit-mate-authentication-agent-1:141982): WARNING **: 15:26:36.829: > atk-bridge: GetRegisteredEvents returned message with unknown signature > > ** (polkit-mate-authentication-agent-1:141982): WARNING **: 15:26:36.829: > atk-bridge: get_device_events_reply: unknown signature > > ** (polkit-mate-authentication-agent-1:141982): WARNING **: 15:26:36.829: > atk-bridge: get_device_events_reply: unknown signature > (uint32 1,) > *** ERROR *** > TI:15:26:39 TH:0x55bef6378ad0 FI:gpm-manager.c > FN:gpm_manager_systemd_inhibit,1786 > - Error in dbus - GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: > Permission denied > Traceback: > mate-power-manager(+0x1d304) [0x55bef5347304] > mate-power-manager(+0x1478b) [0x55bef533e78b] > /lib64/libgobject-2.0.so.0(g_type_create_instance+0x311) > [0x7f90fcf0b1b1] > /lib64/libgobject-2.0.so.0(+0x193f5) [0x7f90fceed3f5] > /lib64/libgobject-2.0.so.0(g_object_new_with_properties+0x275) > [0x7f90fceeeb05] > /lib64/libgobject-2.0.so.0(g_object_new+0xc1) [0x7f90fceef6b1] > mate-power-manager(+0x15e26) [0x55bef533fe26] > mate-power-manager(+0xb20a) [0x55bef533520a] > /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f90fcaa01a3] > mate-power-manager(+0xb58e) [0x55bef533558e] > Traceback (most recent call last): > File "/usr/bin/seapplet", line 34, in <module> > from setroubleshoot.config import get_config > ModuleNotFoundError: No module named 'setroubleshoot.config' > > ** (mate-screensaver:141959): WARNING **: 15:26:39.843: AT-SPI: Could not > obtain desktop path or name > > > ** (mate-screensaver:141959): WARNING **: 15:26:39.844: atk-bridge: > GetRegisteredEvents returned message with unknown signature > > ** (mate-screensaver:141959): WARNING **: 15:26:39.844: atk-bridge: > get_device_events_reply: unknown signature > > ** (mate-screensaver:141959): WARNING **: 15:26:39.845: atk-bridge: > get_device_events_reply: unknown signature > > ** (nm-applet:141855): WARNING **: 15:26:39.972: AT-SPI: Could not obtain > desktop path or name > > > ** (nm-applet:141855): WARNING **: 15:26:39.974: atk-bridge: > GetRegisteredEvents returned message with unknown signature > > ** (nm-applet:141855): WARNING **: 15:26:39.974: atk-bridge: > get_device_events_reply: unknown signature > > ** (nm-applet:141855): WARNING **: 15:26:39.974: atk-bridge: > get_device_events_reply: unknown signature > > ** (evolution-alarm-notify:141952): WARNING **: 15:26:40.409: AT-SPI: > Could not obtain desktop path or name > > > ** (evolution-alarm-notify:141952): WARNING **: 15:26:40.411: atk-bridge: > GetRegisteredEvents returned message with unknown signature > > ** (evolution-alarm-notify:141952): WARNING **: 15:26:40.411: atk-bridge: > get_device_events_reply: unknown signature > > ** (evolution-alarm-notify:141952): WARNING **: 15:26:40.411: atk-bridge: > get_device_events_reply: unknown signature > Initializing caja-open-terminal extension > Initializing caja-xattr-tags extension > Initializing caja-image-converter extension > > ** (emacs:142374): WARNING **: 15:26:54.745: AT-SPI: Could not obtain > desktop path or name > > > ** (emacs:142374): WARNING **: 15:26:54.755: atk-bridge: > GetRegisteredEvents returned message with unknown signature > > ** (emacs:142374): WARNING **: 15:26:54.755: atk-bridge: > get_device_events_reply: unknown signature > > ** (emacs:142374): WARNING **: 15:26:54.755: atk-bridge: > get_device_events_reply: unknown signature > > ** (mate-terminal:145225): WARNING **: 15:36:58.397: AT-SPI: Could not > obtain desktop path or name > > > ** (mate-terminal:145225): WARNING **: 15:36:58.540: atk-bridge: > GetRegisteredEvents returned message with unknown signature > > ** (mate-terminal:145225): WARNING **: 15:36:58.540: atk-bridge: > get_device_events_reply: unknown signature > > ** (mate-terminal:145225): WARNING **: 15:36:58.540: atk-bridge: > get_device_events_reply: unknown signature > > (mate-screensaver:141959): GLib-CRITICAL **: 16:29:53.048: Source ID 57 > was not found when attempting to remove it > > (mate-screensaver:141959): GLib-CRITICAL **: 17:38:18.661: Source ID 101 > was not found when attempting to remove it > > (mate-screensaver:141959): GLib-CRITICAL **: 17:46:13.071: Source ID 161 > was not found when attempting to remove it > > (mate-screensaver:141959): GLib-CRITICAL **: 19:07:25.615: Source ID 213 > was not found when attempting to remove it > ICE default IO error handler doing an exit(), pid = xxxxxx, errno = 32 > > (mate-settings-daemon:141818): GLib-GIO-WARNING **: 20:52:35.368: Error > releasing name org.mate.SettingsDaemon.Rfkill: The connection is closed > [1590348395,000,xklavier.c:xkl_engine_start_listen/] The backend does > not require manual layout management - but it is provided by the application >

1 0

Server/Client Timeout
by brian 26 May '20

26 May '20

I'm using x2go to log into a server that I have woken from a suspended state using a wake-on-lan command. It appears that the server pc is not aware of the x2go connection, and returns to a suspended state shortly after I connect with the x2go client. About 10 minutes. Are there keep-alive settings or time-out parameters, or other means that can be configured is x2go to prevent this from happening? Thanks, brian, ny

2 1

x2goversion problem affecting pyhoca-cli, and a solution
by Michael Ashley 26 May '20

26 May '20

Hi folks, While trying to get pyhoca-cli to work, I noticed that x2goversion on the server was printing out the version numbers without the leading component names. E.g., : 4.1.0.3 : 4.1.0.3 : 4.1.0.3 : 4.1.0.3 : 4.1.0.3 : 3.5.99.23 : 4.1.0.3 instead of: x2goserver: 4.1.0.3 x2goserver-common: 4.1.0.3 x2goserver-extensions: 4.1.0.3 x2goserver-fmbindings: 4.1.0.3 x2goserver-printing: 4.1.0.3 x2goserver-x2goagent: 3.5.99.23 x2goserver-xsession: 4.1.0.3 The problem was that my X2GO_VERSIONS_BASEPATH had a ".." in it, which caused the following line in x2goversion to fail: X2GO_COMPONENT="$(echo "${compfile}" | cut -d '.' -f '2')" A fix is to replace the line with: X2GO_COMPONENT=${compfile#*VERSION.} Finally, to have a working pyhoca-cli, you need to use the version from 11 March 2020 or later https://code.x2go.org/gitweb?p=pyhoca-cli.git;a=tree Regards, Michael

2 1

x2gokdrive: disable menu bar
by Martin Lange 21 May '20

21 May '20

Hello, I am experimenting with x2gokdrive right now. It works great, much faster than nx in a local network. I have only one problem: Is there an option to disable the kdrive menu bar overlay in an active session? I didn't found anything in the wiki. This menu is useful on fat clients, but on thinclients (with x2gothinclient and x2gobroker) it is unnecessary and would confuse my users. Thanks in advance! Martin

4 7

SSH compression
by Simon Reiter 17 May '20

17 May '20

Hi, I already read a few information about the compression used in x2go at https://github.com/ArcticaProject/nx-libs/issues/802. My naive assumption would be that using the compression in x2go makes any compression in the SSH config obsolete, because the compression is only a general one and the one in x2go should suite better for what to be transmitted. Since x2go reads my SSH config, I am now wondering, if the “Compression” option in the config file is ignored when establishing the connection or not. On my current setup, the x2go server requires a ProxyJump, which I set up in the x2go session settings. Does it provide better performance to do it like this or rather open manually a SSH connection to the target host with some local forwarding? And also here with or without compression? I am very happy for some recommendations. Best regards, Simon Reiter

1 0

x2go occasionally stops responding
by Andrew Munn 12 May '20

12 May '20

I can connect to my x2go session running XFCE on CentOS 8.1. The x2go client runs on Windows. Screen updates are still pushed to my client correctly (on-screen clock shows correct time), however sometimes my kb and mouse actions start being ignored. I can disconnect and reconnect to the same session from another windows PC and the results are the same. So something on the CentOS server appears to be the issue, The only way I know to recover is kill the x2go session on the server and reconnect.

1 0

Semi-Offtopic: The sorry state of Landline and Mobile Internet in Germany
by Stefan Baur 11 May '20

11 May '20

Hi List, in an adjacent thread, Alex made a statement that low-bandwidth internet connections are a thing of the past, and thus NX is basically obsolete. I have personal experience to share which proves him wrong. The following internet speeds were recorded in a suburb of a metropolitan area with more than 185 000 residents. And yes, I have the screenshots to prove it, I just don't want to burden the list with them. Residential DSL: Downstream: 5.435 MBit/s max, 5.233 MBit/s average Upstream: 0.465 MBit/s max, 0.427 MBit/s average Ping latency: 23.00 ms min, 28.94 ms average Residential Cable: Downstream: 35.14 MBit/s max, 28.06 MBit/s average Upstream: 2625 MBit/s max, 2.426 MBit/s average Ping latency: 32.00 ms min, 39,38 ms average (iow, higher throughput than DSL, but higher latency) -> This will, however, get worse, as Cable is a shared medium and people in the area are getting fed up with their DSL speeds and are switching over to Cable as their contracts expire. LTE, 1st of 2 providers: 3 out of 5 bars Downstream: 4.715 MBit/s max, 2.029 MBit/s average Upstream: 3.923 MBit/s max, 3.706 MBit/s average Ping latency: 48.00 ms min, 60.50 ms average LTE, 2nd of 2 providers: 2 out of 5 bars Downstream: 0.325 MBit/s max, 0.214 MBit/s average Upstream: 0.325 MBit/s max, 0.225 MBit/s average Ping latency: 64.00 ms min, 79.25 ms average Now step outside and move another 800 meters towards the city limits, and LTE provider 1 drops to UMTS/EDGE (and GSM on a bad day), while LTE provider 2 actually goes up to 3-4 bars and gets 3-7 MBit/s peak rates - but they are short peaks/bursts in an otherwise very mediocre reception. Nothing you want to rely on. Again, this isn't Mooville, West Virgina, with 100 inhabitants and 75 of them cattle, but a larger city in the self-proclaimed high-tech nation Germany. Even Finnish rural areas have better UMTS and LTE coverage than we in Germany have, at the outskirts of our cities. And no, I'm not making this up, I've been to such areas in Finland in the last two years, and I know what the reception there was like. So NX will be here for quite some time, there is a need for it, and for less fancy, but lightweight desktops that work well with it. -Stefan -- 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

6 11

Re: [X2Go-User] Resizing bug
by Kees Bakker 09 May '20

09 May '20

On 07-05-2020 11:48, Ulrich Sibiller wrote: > 1. well, the current source is this one: > https://github.com/ArcticaProject/nx-libs > 2. go to nx-X11/programs/Xserver/hw/nxagent > 3. edit Screen.c and Window.c. find these lines right at the beginning: > #undef TEST > #undef DEBUG > and change them to > #define TEST > #define DEBUG > > If you want to have really much output that tends to get overwhelming > and unreadable you can do the same for Events.c > > 4. in the toplevel directory run debuild -uc -us > > (for other distros see README.NX-development in the toplevel directory) > > 5. Install the resulting packages > 6. run you session, replicate the issue > 7. post ~/.xg2o/<your session>/session.log (maybe strip it a bit) > > Please ask if you have questions/problems. > Thanks Uli Here is a first set of (stripped) logs. The procedure was simple, but is of course not 100% reproducible because the mouse movements can be different each time. But the import condition is that the window is only **moved** by clicking on the top bar and dragging it somewhat to the right and a bit down. After the move, keep the mouse down and keep it there for two or three seconds. Three remote desktops: (standard) Ubuntu, Gnome Classic, MATE. The remote session size is 800x600. The local desktop is 1440x900. To start I have only grepped the lines with "nxagentChangeScreenConfig:" In the case of MATE the bug does not show up, but in the other two cases it does. ===============MATE==================== nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55aa1ec8be60] nxagentChangeScreenConfig: grabstate [SERVER_GRABBED], client [(nil)] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 1,56 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55aa1ec8be60] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55aa1edd4bb0] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 119,99 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55aa1ec8be60] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55aa1edd4bb0] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 300,164 800x600 nxagentChangeScreenConfig: returning [1] ===============MATE==================== ===============Ubuntu=================== nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_GRABBED], client [(nil)] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 67,57 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [630] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 630 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x630 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [660] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 660 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x660 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [690] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 690 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x690 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [720] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 720 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x720 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [750] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 750 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x750 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [780] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x56398886cef0] nxagentChangeScreenConfig: Changing config to 800 x 780 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x780 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [843] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x56398886cef0] nxagentChangeScreenConfig: Changing config to 800 x 843 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x843 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [843] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x56398886cef0] nxagentChangeScreenConfig: Changing config to 800 x 843 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,57 800x843 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [843] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x563988763e40] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x5639888ab690] nxagentChangeScreenConfig: Changing config to 800 x 843 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 439,159 800x843 nxagentChangeScreenConfig: returning [1] ===============Ubuntu=================== ===============Gnome Classic================ nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_GRABBED], client [(nil)] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 0,65 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [600] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 600 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x600 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [637] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 637 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x637 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [674] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 674 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x674 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [711] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 711 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x711 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [748] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 748 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x748 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [785] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 785 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x785 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [801] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 801 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x801 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [801] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 801 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,65 800x801 nxagentChangeScreenConfig: returning [1] nxagentChangeScreenConfig: called for screen [0], width [800] height [801] nxagentChangeScreenConfig: screenInfo.screens[0]->root [0x55efc5939ee0] nxagentChangeScreenConfig: grabstate [SERVER_UNGRABBED], client [0x55efc5a96170] nxagentChangeScreenConfig: Changing config to 800 x 801 nxagentChangeScreenConfig: Xinerama is disabled nxagentChangeScreenConfig: current geometry: 205,132 800x801 nxagentChangeScreenConfig: returning [1] ===============Gnome Classic================ -- Kees

2 1

Fwd: Resizing bug
by Ulrich Sibiller 09 May '20

09 May '20

Sorry, hit the wrong reply button... ---------- Forwarded message --------- From: Ulrich Sibiller <uli42(a)gmx.de> Date: Thu, May 7, 2020 at 11:48 AM Subject: Re: [X2Go-User] Resizing bug To: Kees Bakker <kees(a)ijzerbout.nl> 1. well, the current source is this one: https://github.com/ArcticaProject/nx-libs 2. go to nx-X11/programs/Xserver/hw/nxagent 3. edit Screen.c and Window.c. find these lines right at the beginning: #undef TEST #undef DEBUG and change them to #define TEST #define DEBUG If you want to have really much output that tends to get overwhelming and unreadable you can do the same for Events.c 4. in the toplevel directory run debuild -uc -us (for other distros see README.NX-development in the toplevel directory) 5. Install the resulting packages 6. run you session, replicate the issue 7. post ~/.xg2o/<your session>/session.log (maybe strip it a bit) Please ask if you have questions/problems. Uli BTW: I have not received your email with the "OK lets hear it", I also have checked the spam folder. On Thu, May 7, 2020 at 10:03 AM Kees Bakker <kees(a)ijzerbout.nl> wrote: > > On 04-05-2020 18:00, Kees Bakker wrote: > > On 03-05-2020 21:28, Ulrich Sibiller wrote: > >> I can instruct you how to build a debugging version of > >> nxagent/x2goagent to get more information in the logs. > >> > > OK. Let's hear it. > > Hey, > > I really need some guidance, please. > > I'm familiar how to build things. But I need to know what program(s) to > debug, how to enable more logging, etc. Especially, what are the things > to be looking for? > > I have two virtualbox VMs that I can use, one as the server and one as > the client. I have cloned git://code.x2go.org/nx-libs.git. Is that the one? > -- > Kees > _______________________________________________ > x2go-user mailing list > x2go-user(a)lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user

1 0

new x2go client for windows
by Paul Borowicz 08 May '20

08 May '20

I've been using the 4.1.2.0 windows client with no issues aside from the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem. I just tried the 4.1.2.2 client, hoping it fixed this. It works fine when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report? I see this on the server: Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. : Paul Borowicz

3 9

Re: [X2Go-User] Semi-Offtopic: The sorry state of Landline and Mobile Internet in Germany
by J.Witvliet＠mindef.nl 07 May '20

07 May '20

From: "Михайло Падалка" <misha.cn.ua(a)gmail.com<mailto:misha.cn.ua@gmail.com>> Date: Thursday, 7 May 2020 at 20:56:45 To: "Stefan Baur" <X2Go-ML-1(a)baur-itcs.de<mailto:X2Go-ML-1@baur-itcs.de>> Cc: "x2go users" <x2go-user(a)lists.x2go.org<mailto:x2go-user@lists.x2go.org>> Subject: Re: [X2Go-User] Semi-Offtopic: The sorry state of Landline and Mobile Internet in Germany Hmm... Just tested connection from my home (city with ~300 000 people), Ukraine: 1) Cable connection, the cheapest plan I can get here: Downstream: 24.72 Mbps Upstream: 24.27 Mbps Ping: 6 ms Btw, I can easily get symmetrical 90 Mbps if I need that - just need to switch plan. 2) LTE (3 bars): Downstream: 10.96 Mbps Upstream: 11.89 Mbps Ping: 36 ms DSL gives lower speeds of course, due to old cables most of which are >30 years old. But it's not used much nowadays. Tested with speedtest.net<http://speedtest.net> You need to see it slightly broader. Nice that some lucky ones have Mega bit connections up/down and few ms latency; but tháts not standard. Some have to cope with satellite connection, gprs. And even those with *dsl, cable or fibre, one individual might have 8Mb download. But at the other end, it also has to be uploaded. One single connection is no problem, neither 10, or 100. But when dealing with 10,000 parallel connections you ARE aware of excessive bandwidth usage. Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user