> No. Users can run vncserver and attach to them like you could before, > or you can run Xvnc -inetd, just as a systemd service/socket pair > instead of out of xinetd. > > The black screen problem that you mentioned does sound familiar -- > I've seen it with VNC clients that don't support OpenGL, with the > GNOME desktop (which uses a compositing display manager), it just > crashes when you log in. Looked at this a bit more. There is a crash, but for a different reason: Dec 19 07:59:31 host dbus-daemon: YPBINDPROC_DOMAIN: Domain not bound Dec 19 07:59:31 host dbus-daemon: YPBINDPROC_DOMAIN: Domain not bound Dec 19 07:59:31 host gnome-session-binary[12324]: ERROR: Failed to connect to system bus: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS)#012aborting... Dec 19 07:59:31 host gnome-session: gnome-session-binary[12324]: ERROR: Failed to connect to system bus: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) Dec 19 07:59:31 host gnome-session: aborting... I've seen this before, and the solution was to make sure that the NISDOMAIN is defined in /etc/sysconfig/network. https://marc.info/?l=centos&m=152806243921469&w=2 NIS setup is correct and working, question is why it is being ignored by dbus. After restarting dbus, there is still a crash, but a different log. Dec 19 08:22:30 host org.a11y.Bus: Activating service name='org.a11y.atspi.Registry' Dec 19 08:22:31 host org.a11y.Bus: Successfully activated service 'org.a11y.atspi.Registry' Dec 19 08:22:31 host org.a11y.atspi.Registry: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Dec 19 08:22:31 host dbus[25267]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Dec 19 08:22:56 host gnome-session-binary[28570]: WARNING: Failed to connect to systemd: Error calling StartServiceByName for org.freedesktop.login1: Timeout was reached Dec 19 08:22:56 host kernel: gnome-session-b[28570]: segfault at 8 ip 00000000004216f1 sp 00007ffdfcfc77b0 error 4 in gnome-session-binary[400000+45000] Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: WARNING: Failed to connect to systemd: Error calling StartServiceByName for org.freedesktop.login1: Timeout was reached Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: GLib-GObject-WARNING: invalid (NULL) pointer instance Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: GLib-GObject-CRITICAL: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Dec 19 08:22:56 host gnome-session: gnome-session-binary[28570]: GLib-GIO-CRITICAL: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed Dec 19 08:22:56 host gnome-session-binary[28570]: GLib-GObject-WARNING: invalid (NULL) pointer instance Dec 19 08:22:56 host gnome-session-binary[28570]: GLib-GObject-CRITICAL: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Dec 19 08:22:56 host gnome-session-binary[28570]: GLib-GIO-CRITICAL: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed Dec 19 08:22:56 host dbus[25267]: [system] Failed to activate service 'org.freedesktop.login1': timed out Dec 19 08:22:56 host abrt-hook-ccpp: Process 28570 (gnome-session-binary) of user 14728 killed by SIGSEGV - dumping core