Support for KDE Plasma 5?

[anntz...@gmail.com]

Does TigerVNC support the new KDE Plasma 5 (plasmashell)? I had no problems with KDE4 but now plasmashell crashes on startup when accessed via tigervnc.
I wonder whether the following could be relevant:
http://wiki.x2go.org/doku.php/doc:de-compat
namely, x2go does not support plasmashell due to its requirement of GLX1.3.

Thanks in advance,
Antony

[DRC]

Have you tried running the window manager in VirtualGL? I haven't tried
that with KDE Plasma 5 specifically, but VirtualGL 2.4 now supports
running 3D window managers, and I've tested it with all of the Gnome and
Unity variants I could get my hands on (basically all of the
compiz-based 3D WM's.) If you're willing to be a guinea pig, try
installing VirtualGL and then edit the TigerVNC startup script
(~/.vnc/xstartup), changing

exec /etc/X11/xinit/xinitrc

to

vglrun /etc/X11/xinit/xinitrc

and

exec sh /etc/X11/xinit/xinitrc

to

vglrun sh /etc/X11/xinit/xinitrc

If you have issues, please contact me offline or on the VirtualGL-Users
mailing list. Curious to know if this even halfway works, as I don't
have access to a machine with Plasma 5 on it.

I support TurboVNC, which doesn't even have a GLX extension, so we don't
have a choice but to run compositing WM's using VirtualGL, but even with
X proxies that do support GLX (like TigerVNC), the performance will be
hugely better when using VirtualGL, and the application will get access
to whatever OpenGL features that the server-side GPU supports (including
newer OpenGL/GLX versions, extensions, etc.)

[anntz...@gmail.com]

VGL 2.4 isn't packaged yet by my distro, but I'm on Arch and will just be lazy and wait for a few days for it to be packaged :-) Or could this also work with e.g. VGL 2.3.3?
My .vnc/xstartup actually ends with "exec startkde" (after the required environment variables manipulation), so I guess I'd replace that with "vglrun startkde"?
I'll let you know when I get results, thanks for the fast help!

Antony

[Peter Astrand]

I'm a little bit unsure of which - if any - GLX version is provided by our
official TigerVNC binaries. However, our ThinLinc product which is based
on TigerVNC ships with support for GLX 1.4:

$ glxinfo | grep -i version
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL version string: 2.1 Mesa 10.1.2
OpenGL shading language version string: 1.20

Don't know if this is enough to run Plasma 5 though.

Rgds,
---
Peter Astrand ThinLinc Chief Developer
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linkoping https://facebook.com/ThinLinc
Phone: +46-13-214600 https://google.com/+CendioThinLinc

[DRC]

You definitely need VGL 2.4 for running 3D WM's.

[Antony Lee]

There is definitely some progress when using vglrun (from VGL2.4): plasmashell starts, and I can e.g. start a konsole, but it still crashes sometimes, although non fatally, e.g. when trying to open the K menu: I get an crash handler window, the menu doesn't appear, but the desktop stays "alive".

I set -x on .vnc/xstartup and redirected stderr to a log, which is attached.  While KDE and VGL error/warning messages get mixed up, perhaps there's still something relevant in there?  e.g.

[VGL] WARNING: The OpenGL rendering context obtained on X display

[VGL]    :0 is indirect, which may cause performance to suffer.

[VGL]    If :0 is a local X display, then the framebuffer device

[VGL]    permissions may be set incorrectly.

or

ERROR: ld.so: object 'libdlfaker.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

If this is relevant, I am using a SSH tunnel to run VNC, as described here:

https://wiki.archlinux.org/index.php/Vncserver#Securing_vncserver_by_SSH_tunnels

Thanks in advance,

Antony

--
You received this message because you are subscribed to a topic in the Google Groups "TigerVNC User Discussion/Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tigervnc-users/YzYhD09R_Vo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tigervnc-users+unsubscribe@googlegroups.com.
To post to this group, send email to tigervnc-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-users/54D4A1EE.7000805%40virtualgl.org.

For more options, visit https://groups.google.com/d/optout.

[Pierre Ossman]

The GLX version depends on the version of Xorg used to build TigerVNC.
Xorg 1.8 and newer will support GLX 1.4. Anything older only has GLX
1.2.

So it depends on where you are getting your builds. Most modern systems
should have a sufficiently new Xorg though (1.8 came out in 2010).

Rgds
--
Pierre Ossman Software Development

Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc

583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600 https://plus.google.com/+CendioThinLinc

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Antony Lee]

2015-02-09 3:12 GMT-08:00 Pierre Ossman <oss...@cendio.se>:

On Thu, 5 Feb 2015 17:16:59 -0800 (PST),
anntz...@gmail.com wrote:

> Does TigerVNC support the new KDE Plasma 5 (plasmashell)?  I had no problems with KDE4 but now plasmashell crashes on startup when accessed via tigervnc.
> I wonder whether the following could be relevant:
> http://wiki.x2go.org/doku.php/doc:de-compat
> namely, x2go does not support plasmashell due to its requirement of GLX1.3.
>

The GLX version depends on the version of Xorg used to build TigerVNC.
Xorg 1.8 and newer will support GLX 1.4. Anything older only has GLX
1.2.

So it depends on where you are getting your builds. Most modern systems
should have a sufficiently new Xorg though (1.8 came out in 2010).

Rgds

I'm pretty sure the Arch Linux builds use the most recent Xorg.

Antony