Gerald B. Cox ha scritto: > > On Sat, Jan 7, 2017 at 11:06 PM, Reindl Harald <h.reindl@xxxxxxxxxxxxx > <mailto:h.reindl@xxxxxxxxxxxxx>> wrote: > > Am 08.01.2017 um 07:19 schrieb Ed Greshko: > > Should it be possible to run KDE plasma in a VNC session? > > When I try starting it I get the dialog box... > > Plasma is unable to start as it could not correctly use OpenGL2. > Please check that your > graphic drivers are set up correctly > > > forget it - these days are sadly gone and even if you get it to work it's > unusable since version 5 > > hence i created a "openbox" vncserver.service to at least have some > graphical remote desktop for acting on remote machines when moving the > data over VPN is no option > > > Ed, Harald: > > Not an expert on this by a long shot, but I've been using it for the last few > weeks on a daily basis since I'm away on travel and has been working pretty > good for me. > i am using TigerVNC, and didn't do anything except to add --> exec startkde > <-- to the xstartup file in the .vnc directory. > > Both server and remote are radeon, not sure if that makes a difference or not. > > Now the home system is set to use OpenGL, but when I connect to it remotely it > shows that it is using XRender as the compositor. I didn't do anything to > make that > change, looks like it is done by TigerVNC somehow. > > Again, I just installed and pretty much just added the "startkde" statement.. The renderer of KWin is one thing, but I think that Plasma (or better, the QtQuick 2 that is used by Plasma) requires OpenGL by default (unless you have the new 2D renderer with a recent version of Qt[1]). Maybe Plasma did not start because the VM had no support for an OpenGL driver (like LLVMPipe)? [1] https://blog.qt.io/blog/2015/01/22/introducing-the-qt-quick-2d-renderer/ -- Luigi _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
