Even when you connect via remote desktop, it is just a translation layer to VNC. Nothing wrong with VNC.
There is nothing wrong with VNC itself, no need to get defensive about the protocol.
But in this instance it seems that the translation RDP to VNC is working a lot better than the native VNC connection, assuming that extension is the native connector.
On the other hand why does RDP still work if I remove the extension? That means its either not the native VNC connector, or the RDP implementation is every bit as native as VNC to the VBox server.
/usr/lib/virtualbox/ExtensionPacks/VNC/ExtPack.xml
<?xml version="1.0"?>
<VirtualBoxExtensionPack xmlns="http://www.virtualbox.org/VirtualBoxExtensionPack" version="1.0">
<Name>VNC</Name>
<Description>VNC plugin module</Description>
<Version revision="121806">5.2.10</Version>
<MainModule>VBoxVNCMain</MainModule>
<VRDEModule>VBoxVNC</VRDEModule>
<ShowLicense/>
</VirtualBoxExtensionPack>
Alles anzeigen
The extension also contains the following libs:
/usr/lib/virtualbox/ExtensionPacks/VNC/linux.amd64
-rw-r--r-- 1 root root 5,9K Apr 26 10:56 VBoxVNCMain.so
-rw-r--r-- 1 root root 19K Apr 26 10:56 VBoxVNC.so
So in fact this looks a lot more like an additional extension pack to me than the other way round.
Well, I got a solution that works for me. If an update restores the extension pack and it stops working, I know where to look.