10.11 GNOME 3 Desktop Connection Problems

Problems with starting the GNOME 3 Desktop or X client from a host running a modern Linux operating system can be difficult to diagnose. For the best results, use a supported version of GNOME 3. Reflection X Advantage supports GNOME 3 version 3.28 or greater contained in the following operating systems (or greater versions of these operating systems):

  • RHEL 7.6

  • Fedora 28

  • Ubuntu 18.04

  • SUSE 15 SP2

  • Solaris 11.4 SRU24

Use the following troubleshooting tips for launching X clients successfully in a GNOME 3 environment.

A “sad face” or blank screen appears when the gnome-session client is launched or when connecting with XDMCP

Make sure your session meets the GNOME 3 Desktop Session Definition Requirements. The GNOME 3 Desktop requires extensions that are not required for other sessions.

The desktop fails to launch on systems using the legacy gnome-session command: gnome-session --display %IP#%

The GNOME 3 gnome-session client doesn’t support the --display command line argument. If you need to manually set the DISPLAY environment variable, prefix the client command with DISPLAY=%IP#% as follows.

        (DISPLAY=%IP#% dbus-run-session -- gnome-session &)
      

The desktop fails to launch using older connection types such as Rexec, Rsh or Rlogin

Make sure the client command sets the DISPLAY environment variable for gnome-session:

        (DISPLAY=%IP#% dbus-run-session -- gnome-session &)
      

The desktop fails to launch on systems with Wayland installed

Make sure the GNOME 3 Desktop is launched with a unique D-Bus session by prefixing the X client command with dbus-run-session --

        (dbus-run-session -- gnome-session &)
      

The desktop fails to close when a user logs out of the desktop

Make sure the GNOME 3 Desktop is launched with a unique D-Bus session by prefixing client command with dbus-run-session --

        (dbus-run-session -- gnome-session &)
      

The desktop launches but is very slow to load and refresh the display.

Try the following configuration settings:

The desktop fails to launch when a remote host has proprietary video drivers installed such as NVIDIA

Set __GLX_VENDOR_LIBRARY_NAME=mesa in the environment before launching the command as follows:

        (__GLX_VENDOR_LIBRARY_NAME=mesa dbus-run-session -- gnome-session &)