[
https://issues.apache.org/jira/browse/GUACAMOLE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper resolved GUACAMOLE-262.
--------------------------------------
Resolution: Fixed
Fix Version/s: 0.9.13-incubating
Proposed workaround for [upstream
bug|https://github.com/LibVNC/libvncserver/issues/141] now merged to master.
Hopefully this will be fixed upstream. Either way, I think we should begin
looking into whether we should migrate away from libvncclient entirely. This
issue isn't all that severe, but I'm not sure we're really benefiting from
using libvncclient anymore. It may be better to simply implement VNC directly
ourselves.
> Cannot connect to ESXi 6.5 VNC server
> -------------------------------------
>
> Key: GUACAMOLE-262
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-262
> Project: Guacamole
> Issue Type: Bug
> Components: VNC
> Reporter: Daryl Borth
> Assignee: Michael Jumper
> Priority: Minor
> Fix For: 0.9.13-incubating
>
>
> I was having trouble getting Guacamole to connect to ESX 6.5's VNC server.
> The issue is reported here - https://github.com/LibVNC/libvncserver/issues/141
> Using TightVNC, TigerVNC, UltraVNC, and Chicken of the VNC the connection
> worked fine - only Guacamole failed. After some Wireshark sleuthing I found
> that libvncserver's client by default sets the trueColour flag to TRUE (which
> is -1 which is 255), whereas all of the other clients listed above set this
> flag to 1. Although the spec is vague - it says non-zero is "true" - I would
> suggest setting this flag to 1 to maximize compatibility:
> {code:none}
> void guac_vnc_set_pixel_format(rfbClient* client, int color_depth) {
> client->format.trueColour = 1;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
