Recent Changes - Search:

TurboVNC Home

About TurboVNC

Downloads

Documentation

Reports

Developer Info

Contact

Related Projects

TurboVNC 2.1.x Window Manager Compatibility Report

The following window manager configurations have been tested either by us or by the TurboVNC community using the TurboVNC 2.1.x X server. If you know of any issues that are not described here, please submit a bug report. If you have information about other WM configurations, please contact us.

O/SWindow ManagerKnown Issues
Fedora 24GNOME 3.20.xMust enable 3D window manager support or use Mesa (10.0.5 known to work. Later versions encounter this issue.)

See complete list of known GNOME 3 issues and workarounds here.
 KDE 5.7.xMust enable 3D window manager support with VirtualGL 2.5 or later (Mesa causes plasmashell to crash, for unknown reasons.)
FreeBSD 8.4GNOME 2.32.xNone
FreeBSD 10.3MATE 1.12.xNone
Kubuntu 16.04KDE Plasma 5.5.xMust enable 3D window manager support with VirtualGL 2.5 or later (Mesa causes plasmashell to crash, for unknown reasons.)
Linux Mint 17.2MATE 1.10.xNone
Linux Mint 18KDE Plasma 5.6.xMust enable 3D window manager support with VirtualGL 2.5 or later (Mesa causes plasmashell to crash, for unknown reasons.)
OS XTWMNone
Red Hat Enterprise Linux 4 (and equivalents)GNOME 2.8.xMust add -extension Composite to the vncserver command line to disable the Composite extension

If the Gnome Terminal window is partly off-screen and the screen is resized to a larger size, the previously off-screen portions of the window are not rendered immediately upon resizing the screen, which results in a partially gray title bar. This appears to be a bug in Gnome Terminal.
 KDE 3.3.xWarnings in log about lack of XFree86-Misc extension
Red Hat Enterprise Linux 5 (and equivalents)GNOME 2.16.xNone
 KDE 3.5.xNone
Red Hat Enterprise Linux 6 (and equivalents)GNOME 2.28.xWarnings in log about lack of GLX extension
 KDE 4.3.xWarnings in log about lack of GLX extension
Red Hat Enterprise Linux 7 (and equivalents)GNOME 3.14.x (including Classic)Must enable 3D window manager support or use Mesa (10.0.5 known to work. Later versions encounter this issue.)

See complete list of known GNOME 3 issues and workarounds here.
 KDE 4.10.xNone
 MATE 1.14.x (installed via EPEL)Must add exec mate-session to ~/.Xclients, then chmod 700 ~/.Xclients.
Solaris 10CDE 1.6.xMay need to add -extension Composite to the vncserver command line to disable the Composite extension. 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.
 GNOME 2.6.xMay need to add -extension Composite to the vncserver command line to disable the Composite extension. 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.
Solaris 11GNOME 2.30.xNone
SuSE Linux Enterprise 11GNOME 2.24.xNone
 KDE 4.1.xNone
SuSE Linux Enterprise 12GNOME 3.14.xMust enable 3D window manager support or use Mesa (10.0.5 known to work. Later versions encounter this issue.)

See complete list of known GNOME 3 issues and workarounds here.
Ubuntu 10.04 LTSGNOME 2.30.xNone
Ubuntu 12.04 LTSUnity 2D 5.12.x/5.14.xNone
Ubuntu 14.04 LTSGNOME 3.8.x (fallback)None
 MATE 1.8.xNone
 Unity 7.2.xMust enable 3D window manager support or use Mesa
Ubuntu 16.04 LTSGNOME 3.18.x (flashback-metacity)None
 MATE 1.12.xNone
 Unity 7.4.xMust enable 3D window manager support or use Mesa

See complete list of known Unity 7.4 issues and workarounds here.

3D Window Manangers

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. TurboVNC 2.0 and later includes an option that allows you to easily run these window managers in VirtualGL (VirtualGL 2.4 or later required.) To enable this feature, pass an argument of -3dwm to /opt/TurboVNC/bin/vncserver.

Persistent Screen Resolution

Many window managers provide an applet for specifying the screen resolution. This applet interacts with the X RANDR extension, and since that extension is fully supported in TurboVNC 2.0 and later, the built-in screen resolution applet in the window manager can be used to change the size of the TurboVNC desktop. However, it should be noted that, at least in the case of GNOME and KDE, setting the TurboVNC desktop size in this manner may cause the desktop size to persist when you launch a new TurboVNC session. This is because, when the screen resolution is changed using the screen resolution applet in GNOME and KDE, the applet stores the new value and attempts to set the screen resolution to that value the next time the window manager is launched (effectively circumventing the -geometry argument to vncserver.) Notes on the behavior of specific window managers are included below for reference:

O/SWindow ManagerScreen Resolution Set Using...Screen Resolution PersistencePersistent Resolution Stored In...How to Clear Persistent Resolution
Red Hat Enterprise Linux 5 (and equivalents)GNOME 2.16.xSystem-->Preferences-->Screen ResolutionAlwaysGConf /desktop/gnome/screen/default/0/resolutiongconftool-2 -u /desktop/gnome/screen/default/0/resolution
 KDE 3.5.xControl Center-->Peripherals-->DisplayWhen "Apply settings on KDE startup" is checked in the "Display" applet prior to clicking "Apply"N/AUncheck "Apply settings on KDE startup" in the Display applet, and click "Apply"
Red Hat Enterprise Linux 6 (and equivalents)GNOME 2.28.xSystem-->Preferences-->DisplayAlways. 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.~/.config/monitors.xml, in a configuration node containing <output name="TurboVNC">Edit ~/.config/monitors.xml, removing the TurboVNC configuration node
 KDE 4.3.xSystem Settings-->DisplayOnly when krandrtray is configured to run at login or when the Display applet is relaunched.~/.kde/share/config/krandrrc, in a section named [Screen_*_Output_TurboVNC]Edit ~/.kde/share/config/krandrrc, removing the TurboVNC section
Red Hat Enterprise Linux 7 (and equivalents)KDE 4.10.xSystem Settings-->DisplayOnly when krandrtray is configured to run at login or when the Display applet is relaunched.~/.kde/share/apps/kscreen/{some_unique_id} (grep for "TurboVNC")Remove the file under ~/.kde/share/apps/kscreen/ that corresponds to the TurboVNC output
 MATE 1.14.xSystem-->Preferences-->DisplayAlways. 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.~/.config/monitors.xml, in a configuration node containing <output name="TurboVNC">Edit ~/.config/monitors.xml, removing the TurboVNC configuration node

Creative Commons LicenseAll content on this web site is licensed under the Creative Commons Attribution 2.5 License. Any works containing material derived from this web site must cite The VirtualGL Project as the source of the material and list the current URL for the TurboVNC web site.

Edit - History - Print - Recent Changes - Search
Page last modified on October 21, 2016, at 07:02 PM