Differences

This shows you the differences between two versions of the page.

--- doc:faq:start [2015/08/21 00:36]
mikedep333 NX FAQ -> NX Protocol FAQ
+++ doc:faq:start [2015/08/23 13:13]
ionic Switch to AE...
@@ Line 1: / Line 1: @@
 ====== FAQ ======
-For those who want to find reasons for certain behavious of X2Go, read here: [[http://wiki.x2go.org/doku.php/wiki:development:debugging|How To Debug or Troubleshoot your X2Go installation]]
+For those who want to find reasons for certain behavior of X2Go, read here: [[http://wiki.x2go.org/doku.php/wiki:development:debugging|How To Debug or Troubleshoot your X2Go installation]]
 ===== NX Protocol FAQ =====
@@ Line 8: / Line 8: @@
 No. It is not possible to use NX client to log on to an X2Go server and vice versa.
-Even though X2Go uses the same libraries, X2Go aims for an even greater integration into the Linux environment.
+X2Go does use the same libraries for graphics, keyboard/mouse input, and clipboard sharing. However, X2Go aims for an even greater integration into the Linux environment. Therefore, X2Go performs session handling in an incompatible manner.
 X2Go also performs SSH authentication in a different manner than NoMachine does.
@@ Line 14: / Line 14: @@
 ==== Can I install FreeNX and X2Go Server on one system? ====
-Yes - the NX libraries of X2Go are actually the most recent versions of NXv3 libs available (including our own patch set). NoMachine is about to drop the NXv3 development branch completely and NXv4 will be released as closed source only :-(.
+Yes - the NX libraries of X2Go are actually the most recent stable versions of NXv3 libs available. They are 3.5.0.x. They include the patchset developed by X2Go and [[https://github.com/ArcticaProject/nx-libs|others]]. NoMachine dropped the NXv3 development branch completely and NXv4 was released as closed source only :-(.
-Due to these circumstances in the future the X2Go project will be upstream source for NXv3 libs for quite some distributions like Debian or Ubuntu.
 In former times the NX libs shipped with X2Go installed into an X2Go'ish location so that they would not interfere with the original NX libraries.
@@ Line 22: / Line 20: @@
 Nowadays the NX libs shipped with X2Go work as a replacement for the NXv3 that are not maintained by NoMachine anymore.
-(This FAQ article has been written by Mike Gabriel, if someone does not agree with the given information on NoMachine, please be so kind to contact me, so that we can discuss it and possibly correct errors in the given information).
+(This FAQ article has been written by Mike Gabriel and Mike DePaulo. If someone does not agree with the given information on NoMachine, please be so kind to contact us, so that we can discuss it and possibly correct errors in the given information).
-==== Why are you using the terms "nx-libs" and "NX libraries" when X2Go uses the 2 executables nxproxy & nxagent?  ====
+==== Why are you using the terms "nx-libs" and "NX libraries"? X2Go clearly uses the 2 executables nxproxy & nxagent?  ====
 Basically:
@@ Line 45: / Line 43: @@
 Having separate tarballs made maintenance more difficult, so they were combined into one as the X2Go project started redistributing them.
+==== Why not just use X11 forwarding over SSH? This is what Keith Package recommended. ====
+You are probably referring to the [[http://keithp.com/~keithp/talks/lbxpost/|LBX post-mortem]]
+It is true that X11 forwarding's performance can be improved by SSH's zlib compression and by the use of XCB rather than xlib.
+However, nx-libs performs 3 additional performance improvements:
+  - nx-libs caches images, so that they do not have to be resent. For example, opening up your "start menu" is very fast the 2nd and 3rd time that you do so.
+  - zlib is generic lossless compression, so it is not well-suited for images. nx-libs achieves better performance by using compression methods such as JPEG (default, lossy) or PNG (lossless.)
+  - XCB applications are still partially hindered by round-trips, and nx-libs eliminates more of those round-trips. See  [[https://lwn.net/Articles/343506/|Bart Massey's explanation]] for more info.
+The 1st 2 performance improvements also reduce bandwidth usage; which has the effect of improving performance when other users are sharing the same WAN link.
+==== Why Am I told to enable X11 forwarding with X2Go? I thought that X2Go uses nx-libs instead of X11 forwarding! ====
+The simple answer is that the OpenSSH server treats the connection differently (in such a way that degrades nx-libs performance) unless X11 forwarding is enabled.
+[[https://www.nomachine.com/AR05D00391|See NoMachine's explanation for more info.]]
 ==== What is the difference to LTSP? Why a free thin client environment? ====
@@ Line 50: / Line 68: @@
 LTSP requires a high bandwidth on your network. It can efficiently be used in Local Area Networks (LANs) only.
-However, X2Go is not a mere solution for local area networks, but it also allows for the integration of a mobile network into the system. Nomachine’s NX libraries - used by X2Go - enable the transport of whole desktop sessions over a narrow bandwith connection through the internet.
+However, X2Go is not a mere solution for local area networks, but it also allows for the integration of a mobile network into the system. Nomachine’s NX libraries - used by X2Go - enable the transport of whole desktop sessions over a narrow bandwidth connection through the internet.
 Further bonuses of X2Go are that you can pause a desktop session and take it to a different thin client for further use.
@@ Line 74: / Line 92: @@
 Yes, there are two: [[doc:installation:x2goclient#ms_windows|X2Go Client]] and [[doc:installation:pyhoca-gui#ms_windows|PyHoca-GUI]].
-==== Is there a MacOS Client? ====
+==== Is there an OS X Client? ====
 [[doc:installation:x2goclient#macos_x|Yes!]]
@@ Line 106: / Line 124: @@
 This happens because of a package called ''kscreen''. If you encounter an X2Go session trying to launch KDE and this KDE session won't resize properly to your client-side screen or session window size.
-In general, this is not a bug. Using two applications that handle display
+In general, this is not a bug. Using two applications that handle display resolution is not supported, as it can lead to many unexpected situations and race conditions.
-resolution is not supported, as it can lead to many unexpectable situations and
-race conditions.
-On machines that act as X2Go Server only, it may make sense removing the kscreen package completely. This, however, may have an effect on your X2Go server's plug'n'play capabilities. The ''kscreen'' package handles hotplugging of display hardware. So if your X2Go Server machine is used locally, as well as via X2Go, consider well, if it is ok to remove that package or not.
+On machines that act as X2Go Server only, it may make sense removing the kscreen package completely. This, however, may have an effect on your X2Go server's plug'n'play capabilities. The ''kscreen'' package handles hotplugging of display hardware. So if your X2Go Server machine is used locally, as well as via X2Go, consider well, if it is OK to remove that package or not.
 For X2Go we suggest disabling the KScreen KDED module (System Settings ->
@@ Line 149: / Line 165: @@
 At this time libssh, the ssh library used by X2Go is unable to work with an ECDSA key.
-However you may use an RSA key--if you need to--or go with the SSH default authenticating method using the remote user's password.
+However you may use an RSA key - if you need to - or go with the SSH default authenticating method using the remote user's password.
 ==== SSH Login issue ====
-If you already use openssh to get a shell on your x2go server, you may get this message when trying to connect with x2go:
+If you already use OpenSSH to get a shell on your x2go server, you may get this message when trying to connect with x2go:
 <code>
 The host key for
@@ Line 160: / Line 176: @@
 </code>
-This is related to the ECDSA Key (see FAQ above).
+This is related to the ECDSA host key (see FAQ above - although there is a subtle difference between host and client keys.)
-To solve this issue, you can disable ECDSA keys on your ssh server configuration, by commenting the following line in /etc/ssh/sshd_config file:
+To solve this issue, you can disable ECDSA keys on your OpenSSH server configuration, by commenting the following line in /etc/ssh/sshd_config file:
 <code>
 #HostKey /etc/ssh/ssh_host_ecdsa_key
@@ Line 183: / Line 199: @@
 </code>
-==== Libreoffice performance ====
+==== LibreOffice performance ====
-If when using Libreoffice, text selections and copy/paste operations make your X use lots of cpu, disable anti-aliasing and selection transparency on Libreoffice options.
+If when using LibreOffice, text selections and copy/paste operations spike your CPU usage, disable anti-aliasing and selection transparency in the LibreOffice options.
-==== Mate and numlock erratic behaviour ====
+==== Mate and numlock erratic behavior ====
-If using Mate DE, your numlock key makes numeric keyboard act in a numeric manner or as a moviment keys, disable the dconf setting with:
+If using Mate DE, your numlock key makes numeric keyboard act in a numeric manner or as a movement keys, disable the dconf setting with:
 <code>
 gsettings set org.mate.peripherals-keyboard remember-numlock-state false

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools