[
https://issues.apache.org/jira/browse/GUACAMOLE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356012#comment-16356012
]
Michael Jumper commented on GUACAMOLE-340:
------------------------------------------
Perhaps, though my suspicion is that a different encoding is being selected
when Guacamole connects vs. another VNC client. I see two main possibilities:
# The VNC server is selecting a different encoding when it receives a
connection from libvncclient, due to libvncclient not supporting the same
encodings, and does not handle that encoding correctly.
# libvncclient itself does not implement the encoding correctly.
Either way, migrating away from depending on libvncclient may be the only
solution here. Besides likely solving this issue, there are other features
which we cannot add so long as VNC depends on that library like VNC-over-SSH
(GUACAMOLE-312).
> VNC slow and much of screen is black
> ------------------------------------
>
> Key: GUACAMOLE-340
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-340
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 0.9.12-incubating
> Environment: ChromeOS
> Reporter: Matt Prager
> Priority: Major
> Attachments: Screenshot 2017-07-06 at 9.33.46 AM.png, Screenshot
> 2017-07-06 at 9.34.16 AM.png
>
>
> The screenshots below show the issue best. Exact same computer and server. In
> one screenshot, using RealVNC's viewer, it looks great; using Guacamole, it's
> covered with black splotches. I'm not sure how to debug this as it's
> obviously not an issue with the connection or the VNC server (I'm using
> UltraVNC) since the one viewer works fine, but let me know what information
> you need to help figure out why this is happening.
> My VNC settings in Guacamole are nothing more that the minimum required
> (port, username, password).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
