I installed Plasma 5.7 on Fedora 24, and it does seem to be very sensitive to the particulars of the OpenGL implementation. In my testing, plasmashell always crashes when I try to use the Mesa Gallium Xlib driver (with this procedure: http://www.turbovnc.org/Documentation/Mesa. Tested with Mesa 10.0.5 and 12.0.1.) However, Plasma 5.7 seemed to work fine with VirtualGL. The caveat here is that I'm not able to test it with a real GPU. I can only test it with Parallels Desktop, so that means that VirtualGL is redirecting the OpenGL context to display :0, and the Parallels Tools are re-re-redirecting the OpenGL calls from the guest to my Mac host. It is entirely possible that it is failing on your system due to particulars of your graphics environment that I can't reproduce. Are you using an nVidia GPU?
Also, within the past week or so, I have made numerous changes to TurboVNC to support GNOME 3, and it's possible that one of those changes fixed the issue you were having with Plasma. It would be worth re-testing the latest code in Git master. Be sure to blow away ~/.vnc/xstartup.turbovnc before you do that, since many of the changes were implemented in the default xstartup.turbovnc file. Long and the short of it, though-- Plasma 5.7 does indeed require OpenGL, and there doesn't appear to be a way around it. I'm not really surprised. This situation with KDE Plasma and GNOME will get worse as those WMs move more in the direction of Wayland. I am looking at the possibility of incorporating an (unaccelerated) GLX extension into the next major release of TurboVNC, solely for the purpose of supporting 3D window managers. But that's a problem for another day. If you can verify that you're still having the same issue with the code in Git master, then please send me the following: -- A description of your graphics environment (GPU model and driver revision, mainly) -- The contents of the TurboVNC log file from a session in which Plasma fails to start -- A screenshot of the error it is giving you I'll file a GitHub issue with that information in order to track it. Unfortunately, that's probably all I'll be able to do for TurboVNC 2.1. On 7/21/16 8:12 AM, Joshua Anderson wrote: > Has anyone had luck getting KDE Plasma 5.7 to work in a TurboVNC > server? I get an error that Plasma is unable to start because it > cannot use OpenGL 2. > > I tried disabling compositing and opengl in xstartup: > export KWIN_COMPOSE=N > export QT_XCB_FORCE_SOFTWARE_OPENGL=1 > exec startkde; exit > > I tried running startkde with vglrun (the system is configured and > working to use vglrun). I tried with -3dwm to vncserver, I tried to > disable compositing with -extension Composite. Nothing seems to > convince Plasma to stop searching for OpenGL, and for reasons I don't > understand vglrun doesn't seem to make it happy. This is unfortunate > because earlier versions of KDE always played nicely with VNC and > didn't have a hard requirement on opengl, unlike some other window > managers. > > I am running turbovnc v2.0.2, and an install of KDE Plasma 5.7 in Gentoo.
------------------------------------------------------------------------------
_______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
