Hello!
I'm having the same issue, only in version 1.5.2 (no upgrade, clean
install, previous versions worked fine) when connecting RDP to virtual
Windows 2022 servers (Hyper-V)
Try using a lower screen resolution, preferably standard sizes (ie
1024x768) in my case that worked
Kind regards,
El 2023-11-06 16:09, Michael Jumper escribió:
On 11/6/2023 1:56 PM, Allen Chen wrote:
Hi there,
After I upgraded guacamole from 1.2 to 1.5.3, scrolling content is
overwriting itself in RDP session. I googled and found a similar issue
https://www.reddit.com/r/archlinux/comments/ajac8i/scrolling_terminal_content_is_overwriting_itself/.
Server environments: CentOS 7.7, tomcat 8, jdk-13 and Apache proxy as
the front end with SSL configured to redirect https to guacamole port
8080
Test 1: downgrade guacamole client to 1.3 and keep guacd on 1.5.3,
scrolling content is working properly both via Apache proxy and direct
access on port 8080;
Test 2: downgrade guacamole client to 1.4 and keep guacd on 1.5.3,
scrolling content is not working properly via Apache proxy, but
working properly via direct access on port 8080;
So the problem is on version 1.4 and 1.5.3 via Apache proxy.
To confirm this, I build a new machine with CentOS Stream release 8,
tomcat 9 and jdk-20, I get exactly the same results listed in Test 1
and Test 2.
I took a screenshot:
Does anybody know what is the issue?
The presence/absence of a proxy has no bearing on the graphical content
of a connection. The only case where a proxy might affect only the
handling of graphical content would be if that proxy adds HTTP headers
that instruct the browser to disallow such content from being decoded
("Content-Security-Policy").
I don't think the above is likely. There would be errors/warnings in
your browser's console if that's the case, and it would probably result
in the connection rendering absolutely nothing. From your screenshots,
things are definitely being rendered.
This looks more like a bug in the remote desktop server hosting the
session (ie: incorrect graphical updates are being sent). I think the
correlations that you're seeing between proxy vs. no proxy, various
releases of Guacamole itself, different versions of Tomcat or the JDK,
etc. are more likely coincidences.
If you can narrow things to purely one version of guacd that works and
another that doesn't, changing absolutely nothing else in the stack
whatsoever, then that could indicate a problem in the handling of
graphical updates or a bug in one of the lower-level libraries that we
consume. I don't think this is likely either, though, as it would have
been loudly noticed by others by now:
https://guacamole.apache.org/faq/#probably-not-a-bug
If you *can* narrow things to a known-good release and a known-bad
release, then a git bisect should reveal the nature of the issue.
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org
