The next release of ThinLinc is almost ready. Before the official launch of version 4.21.0, we’re making a beta build available for public testing. This beta includes over 100 fixes and improvements. Some of the most prominent changes are:
ThinLinc Web Access now supports the OpenID Connect authentication
protocol. This enables organizations to delegate authentication to
solutions like Keycloak or Microsoft Entra ID, allowing convenient
single sign-on, and more flexibility in authentication methods and
policy.
ThinLinc session logs are now in the system journal instead of in
xinit.log in the ThinLinc session directories. This avoids multiple
log locations for modern Linux systems, and gives more flexibility
when analyzing logs.
It is now possible to configure the ThinLinc client with mandatory
settings on managed endpoint devices. These settings will be forced
and cannot be overridden by the user.
The Linux ThinLinc client now supports 64-bit ARM (ARM64),
replacing the previous 32-bit ARM client. This improves
compatibility with modern ARM hardware and operating systems.
The platform requirements for the ThinLinc client on macOS have
been raised. It now requires macOS Ventura (version 13) or newer.
Users on older versions of macOS will need to upgrade their
operating system to use this version of the ThinLinc client.
Is there any update on when we will get accelerated 3D support directly from TigerVNC rather than going through VirtualGL? It has been nearly two years now since it was suggested that this would be an upcoming feature. This would be the biggest quality of life improvement for our users by quite some margin.
The feature is actually there in upstream TigerVNC, but the main issue is that it doesn’t work with the proprietary NVIDIA drivers, for reasons which are somewhat beyond our control. Given NVIDIA’s market share, we figured that this would be too much of a “caveat” to warrant including the feature in ThinLinc at this stage. Hope that clarifies things.
Last time I looked, this was due to a lack of support in the NVIDIA drivers for DRI3. That is no longer the case, so er, what is the holdup? The TL;DR is that Wayland basically forced NVIDIA’s hand.
These discuss the lack of DRI3 in the proprietary NVIDIA driver and are from posts well over a year old. As I said DRI3 v1.2 is now INCLUDED in the proprietary NVIDIA driver. I posted a link for you to know I was not making things up. It would appear Cendio is working with out of date information and consequently unnecessarily holding back the transparently accelerated OpenGL feature.