MATE seems to want to aggressively maintain the new resolution once it is set, and this can cause an infinite desktop resize loop if using the TurboVNC Viewer with automatic desktop resizing enabled, and if attempting to set the server's resolution to a size larger than the viewer can display.Įdit ~/.config/monitors. Remove the file under ~/.kde/share/apps/kscreen/ that corresponds to the TurboVNC outputĪlways. ~/.kde/share/apps/kscreen/ (grep for "TurboVNC") ~/.kde/share/config/krandrrc, in a section named Įdit ~/.kde/share/config/krandrrc, removing the TurboVNC section Only when krandrtray is configured to run at login or when the Display applet is relaunched. ~/.config/monitors.xml, in a configuration node containing Įdit ~/.config/monitors.xml, removing the TurboVNC configuration node GNOME 2.28.x seems to want to aggressively maintain the new resolution once it is set, and this can cause an infinite desktop resize loop if using the TurboVNC Viewer with automatic desktop resizing enabled, and if attempting to set the server's resolution to a size larger than the viewer can display. Uncheck "Apply settings on KDE startup" in the Display applet, and click "Apply"Īlways. When "Apply settings on KDE startup" is checked in the "Display" applet prior to clicking "Apply" Gconftool-2 -u /desktop/gnome/screen/default/0/resolution GConf /desktop/gnome/screen/default/0/resolution It is generally recommended that a 2D window manager, such as MATE or Xfce, be used with TurboVNC, but you can also improve the performance of 3D window managers by running them using VirtualGL (VirtualGL 2.4 or later required.) To enable this feature, pass an argument of -vgl to /opt/TurboVNC/bin/vncserver.
The TurboVNC Server includes a software OpenGL implementation that can be used to run these window managers, but the performance will not be stellar. Some recent window managers (GNOME 3 and Unity, in particular) require OpenGL in order to run, and other window managers may optionally require OpenGL in order to enable desktop effects. See complete list of known Unity 7.4 issues and workarounds here
Use sudo apt-get install ubuntu-mate-desktop to install the complete Ubuntu MATE desktop environment. NOTE: This installs the basic window manager. > sudo apt-get install ubuntu-mate-desktop > sudo apt-get install ubuntu-mate-core ubuntu-mate-desktop include contains header files specific to the X Server program, such as graphics context structures. This is the primary directory that Cygwin/X programmers will be interested in.
xwin contains the source code for the Cygwin/X X Server.
> sudo apt-add-repository ppa:ubuntu-mate-dev/precise-mate xquartz contains the source code for the XQuartz X Server, which runs on Mac OS X. > sudo apt-add-repository ppa:ubuntu-mate-dev/ppa SuSE Linux Enterprise 15 (and equivalents) X11 forwarding seems to work fine, though I do see this message: Xlib: extension RANDR missing on display localhost:10.0. This is not necessary in order to run the window manager itself, but it may be necessary in order to work around issues with certain applications. May need to add -extension Composite to the vncserver command line to disable the Composite extension. Red Hat Enterprise Linux 8 (and derivatives) Red Hat Enterprise Linux 7 (and derivatives) Red Hat Enterprise Linux 6 (and derivatives)
GLX extension not enabled (Mesa package provided by the O/S is too old) Red Hat Enterprise Linux 5 (and derivatives) OpenGL does not work, for unknown reasons > sudo dnf group install mate-desktop-environment See complete list of known GNOME 3 issues and workarounds here # Prox圜ommand ssh -q -W %h:%p the window manager using VirtualGL to improve performance # /etc/ssh/ssh_config.d/ which will be automatically included below # To modify the system-wide ssh configuration, create a *.conf file under # list of available options, their meanings and defaults, please see the
# Site-wide defaults for some commonly used options. # configuration file, and defaults at the end. # Thus, host-specific definitions should be at the beginning of the # Any configuration value is only changed the first time it is set. # Configuration data is parsed as follows: # users, and the values can be changed in per-user configuration files # This is the ssh client system-wide configuration file. Here is a comparison of the output of /etc/ssh/ssh_config. On all distrios due to the nvidia driver. Or, you're running GNOME under a Wayland session. it's providing "real" authentication data).
I'm wondering whether Manjaro is actually behaving correctly (e.g. etc/ssh/ssh_config) and see if Ubuntu/Fedora have a different set of forwarding options. You could compare the various software versions and configuration files (e.g. If it's identical then it's identical, so I'm not sure.