You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On modern Linux distributions, GDM runs Xwayland on Display :1024 if
WaylandEnable=true (the default), and it runs Xorg on Display :0 if
WaylandEnable=false. Referring to
aa5ff87 and #94, in 2019 I observed
that it was necessary on RHEL 8 and Fedora 27-28 to add/uncomment
WaylandEnable=false in order for VirtualGL's greeter autostart script
to work. However, that is apparently no longer necessary. In 2025,
using Display :1024 seems to work fine on RHEL 7-10, Ubuntu 16-24,
Fedora 40-42, and openSUSE 15. (In fact, it is necessary on RHEL 10,
since GDM no longer allows Wayland to be disabled. That is what
prompted this change.)
@@ -921,10 +921,6 @@ <h2 id="hd006001">6.1 Initial System Configuration</h2>
921
921
and 3D X server at boot time. This is the default with most modern
922
922
Linux and Unix distributions.</p>
923
923
924
-
<divclass="important"><pclass="important">
925
-
On Wayland-enabled Linux machines running GDM, configuring the machine for use with the GLX back end will disable the ability to log in locally with a Wayland session. In general, logging in locally once the machine has been configured for use with the GLX back end is discouraged, as this could disrupt VirtualGL’s connection to the 3D X server and thus cause OpenGL applications running with VirtualGL to abort or freeze.
926
-
</p></div>
927
-
928
924
<p>3. Accelerated OpenGL is working properly in the 3D X server.</p>
929
925
930
926
<ulclass="Itemize">
@@ -969,8 +965,10 @@ <h2 id="hd006002">6.2 GLX Back End: Granting Access to the 3D X Server</h2>
969
965
need to use the GLX back end. Unless you fully trust the users to whom
970
966
you are granting this access, then you should avoid logging in locally
971
967
to the 3D X server (particularly as root) unless absolutely necessary.
972
-
(Logging in locally to the 3D X server is discouraged anyhow, for
973
-
reasons explained in the previous section.)</p>
968
+
(In general, logging in locally once the machine has been configured for
969
+
use with the GLX back end is discouraged, as this could disrupt
970
+
VirtualGL’s connection to the 3D X server and thus cause OpenGL
971
+
applications running with VirtualGL to abort or freeze.)</p>
974
972
975
973
<p>This section will explain how to configure a VirtualGL server such that
976
974
selected users can use the GLX back end, even if the server is sitting
lists all valid EGL device IDs and their associated DRI device paths.
3125
+
<divclass="important"><pclass="important">
3126
+
<code>vglrun</code> automatically sets <code>VGL_DISPLAY</code> to <code>:1024</code> if <code>VGL_DISPLAY</code> is unset, X Display :1024 exists, and X Display :0 does not exist. This allows VirtualGL to use the GDM greeter’s Xwayland instance as a 3D X server.
0 commit comments