On Thu, Aug 21, 2025 at 9:38 AM 冰红糖 <[email protected]> wrote:
> Hi all, > > Following up on the resize issue, here is a summary of what I have > verified and tested so far: > > - Server: Guacamole 1.5.5 (guacd 1.5.5) deployed on Kylin 10 VM > - Client: Custom web client, where I use Java to configure > `resize-method` > - Remote system: Windows Server 2016 / 2019 > - On the server side, guacd.log shows: "Resize method: display-update" > - On the frontend side, I use a `ResizeObserver` which calls > `guac.sendSize(width, height)` whenever the browser window changes size > - I have confirmed that `resize-method` is not hardcoded on the client > side, but configured via Java (on the server side configuration) > > So far, everything seems correctly configured, but the dynamic resize > behavior is still not working as expected. > > Again, what does "not working as expected" mean? You don't see a resize at all? Or it happens but something else happens - it's wrong, or delayed, etc.? > I would appreciate some guidance on the following points: > > 1. Regarding the **guacamole-client source code**: > - Which part of the codebase should I review to better understand how > the `sendSize()` call from the frontend is handled and passed to `guacd`? > > The code that handles it in the main client is here: https://github.com/apache/guacamole-client/blob/457e3a583e0095c063833fad1e35c374ea9c5f67/guacamole/src/main/frontend/src/app/client/directives/guacClient.js#L444-L472 > 2. Regarding **enabling guacd debug mode**: > - What is the proper way to enable debug logging for `guacd`? > - Is there any official documentation on enabling debug and > interpreting logs, particularly for checking if resize messages are being > received by `guacd`? > > Enabling debugging is describe in the manual: https://guacamole.apache.org/doc/gug/configuring-guacamole.html#configuring-guacd I don't think there's anything specific to resize messages, you'll just have to bump up the log level to either debug or trace and see what you get. On the web/front-end side there's nothing specific to Guacamole, you'll just need to use the standard tools you'd use in JavaScript - logging to the console, breakpoints and watches, etc. -Nick
