The only "error" in the vncserver log file is: gnome-session-is-accelerated: No hardware 3D support. gnome-session-check-accelerated: Helper exited with code 256 gnome-session-is-accelerated: No hardware 3D support. gnome-session-check-accelerated: Helper exited with code 256
** (process:18171): WARNING **: software acceleration check failed: Child process exited with code 1 I assume this is to be expected if not using -3dwm, correct? The Windows TurboVNC client log looks OK: WinTab library not available Connected to eddie port 5911 RFB server supports protocol version 3.8 Connected to RFB server, using protocol version 3.8 Authentication scheme: Standard VNC authentication Authentication successful Desktop name "TurboVNC: eddie:11 (cms0620)" Enabling GII Enabling continuous updates Enabling continuous updates Kind regards, Curt On Monday, January 29, 2018 at 2:12:36 PM UTC-5, curts wrote: > > OK, I've installed MATE, changed from GDM to LightDM, and verified both > are working on the console. I've also created a .dmrc file in my home > directory with the contents: > [Desktop] > session=mate > > I've removed the -3dwm option from the vncserver invocation, but I still > get the "Oh no!" screen when I try to connect remotely using TurboVNC. What > else could be getting in the way? > > Kind regards, > > Curt > > On Thursday, January 25, 2018 at 2:22:08 PM UTC-5, DRC wrote: >> >> In my testing (https://turbovnc.org/Documentation/Compatibility), GNOME >> 3 works with -3dwm, so I'm not sure why it isn't working for you, but >> also, GNOME 3 is not an ideal window manager to use in a VNC >> environment. It's a compositing window manager, so even if you get it >> working, it will be slow, and there are a handful of known issues with >> it in a VNC environment >> ( >> https://github.com/TurboVNC/turbovnc/issues?utf8=%E2%9C%93&q=label%3A%22GNOME%203%22). >> >> >> Some have workarounds, but not all. >> >> My suggestion would be to install and enable MATE using the instructions >> here: >> https://turbovnc.org/Documentation/Compatibility >> (under "Red Hat Enterprise Linux 7 (and equivalents)"). That will give >> you a similar window manager to the GNOME 2 window manager that you used >> with RHEL 6 (MATE is a fork of GNOME 2.) MATE is a 2D window manager, >> so it will run in TurboVNC without -3dwm. If you absolutely need to use >> GNOME 3, then try the dev/2.2 evolving pre-release build >> (https://turbovnc.org/DeveloperInfo/PreReleases), which has a built-in >> software OpenGL implementation that (again, in my testing) works with >> GNOME 3 without using -3dwm (although, again, performance will not be >> stellar.) >> >> DRC >> > -- You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/7bb63ecf-3557-49be-a6f3-f0209805f8d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
