[
https://issues.apache.org/jira/browse/GUACAMOLE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973262#comment-15973262
]
Michael Jumper edited comment on GUACAMOLE-253 at 4/18/17 6:45 PM:
-------------------------------------------------------------------
Well, so far I still have no luck reproducing this issue.
I'd be interested to hear if anyone else in the community has encountered the
same problem, but as long as the bug remains unreproducible, there is no way to
explain what's happening in your case. My suspicion is, of course, that the
problem lies within your VNC server, but if you're absolutely sure that's
impossible, then the next likely explanation would be that this is a bug in
libvncclient.
There's not much going on in Guacamole when it comes to reverse VNC
connections, and not much that can fail on the Guacamole side. The relevant
code is really just a single function call:
https://github.com/apache/incubator-guacamole-server/blob/c4903a8e36eabbaec20ee83a422f599b9db77358/src/protocols/vnc/vnc.c#L113-L125
On GUACAMOLE-262, I suggested that we look into migrating away from
libvncclient. If we do so, that could be a means of solving this, assuming the
problem does indeed reside there. Being able to more directly investigate and
fix bugs in the handling of the VNC protocol would be another good reason for
that migration.
was (Author: mike.jumper):
Well, so far I still have no luck reproducing this issue.
I'd be interested to hear if anyone else in the community has encountered the
same problem, but as long as the bug remains unreproducible, there is no way to
explain what's happening in your case. My suspicion is, of course, that the
problem lies within your VNC server, but if you're absolutely sure that's
impossible, then the next likely explanation would be that this is a bug in
libvncclient.
There's not much going on in Guacamole when it comes to reverse VNC
connections, and not much that can fail on the Guacamole. The relevant code is
really just a single function call:
https://github.com/apache/incubator-guacamole-server/blob/c4903a8e36eabbaec20ee83a422f599b9db77358/src/protocols/vnc/vnc.c#L113-L125
On GUACAMOLE-262, I suggested that we look into migrating away from
libvncclient. If we do so, that could be a means of solving this, assuming the
problem does indeed reside there. Being able to more directly investigate and
fix bugs in the handling of the VNC protocol would be another good reason for
that migration.
> ReverseVNC mouse missing or screen not updated
> ----------------------------------------------
>
> Key: GUACAMOLE-253
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-253
> Project: Guacamole
> Issue Type: Bug
> Components: VNC
> Affects Versions: 0.9.11-incubating
> Environment: Azure - Ubuntu 16.04 2 Cores 4GB RAM
> Reporter: KokHooi Chew
> Priority: Critical
>
> Missing mouse cursor or screen not updated when using ReverseVNC. Tested with
> Remmina + libvncclient and it's working fine all the time
> Another issue is with the listen-timeout(I set 60000) for ReverseVNC. The
> longer Guacamole wait for server connection request, the higher the chances
> of missing mouse cursor or screen not updated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
