You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Matt Boothman (Jira)" <ji...@apache.org> on 2021/02/28 12:59:00 UTC

[jira] [Created] (GUACAMOLE-1304) Is guac 1.3 failing to report actual resolution on vmconnect initial connection?

Matt Boothman created GUACAMOLE-1304:
----------------------------------------

             Summary: Is guac 1.3 failing to report actual resolution on vmconnect initial connection?
                 Key: GUACAMOLE-1304
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1304
             Project: Guacamole
          Issue Type: Bug
          Components: guacamole
    Affects Versions: 1.3.0
         Environment: Debian buster
            Reporter: Matt Boothman


I have an issue when connecting to VMs where the resolution is set differently to the normal 1024x768 resolution. The JS client doesn't receive a second `size` (command?) from the java client, as it used to in our old 0.9.14 installation.

Steps to reproduce:
 # Create a Windows 10 VM in Hyper V (or graphical Linux, I don't think guest OS matters)
 # Connect to the VM from guacamole, without enhanced mode
 # Set the VM resolution to 1152x864 (the display is resized accordingly
 # Disconnect the cuacamole session
 # Reconnect the guacamole session
 # VM display failes to appear

Versions:
 * Guacamole, everything 1.3
 * Hyper-V Server 2019, Windows 10, no version change for hyper-v between upgrade from 0.9.14 and 1.3
 * FreeRDP version 2.2 (buster backports)

Guacd debug:

Guacd is receiving the updated resolution from FreeRDP, and I checked FreeRDP using xfreerdp which works as expected. Debug logs, that I think are relevant, are:

```

Feb 28 10:37:00 guactest guacd[4519]: Sending
Feb 28 10:37:00 guactest guacd[4519]: BitmapCapabilitySet (length 24):
Feb 28 10:37:00 guactest guacd[4519]: #011preferredBitsPerPixel: 0x0010
Feb 28 10:37:00 guactest guacd[4519]: #011receive1BitPerPixel: 0x0001
Feb 28 10:37:00 guactest guacd[4519]: #011receive4BitsPerPixel: 0x0001
Feb 28 10:37:00 guactest guacd[4519]: #011receive8BitsPerPixel: 0x0001
Feb 28 10:37:00 guactest guacd[4519]: #011desktopWidth: 0x0400
Feb 28 10:37:00 guactest guacd[4519]: #011desktopHeight: 0x0300
Feb 28 10:37:00 guactest guacd[4519]: #011pad2Octets: 0x0000
Feb 28 10:37:00 guactest guacd[4519]: #011desktopResizeFlag: 0x0001
Feb 28 10:37:00 guactest guacd[4519]: #011bitmapCompressionFlag: 0x0001
Feb 28 10:37:00 guactest guacd[4519]: #011highColorFlags: 0x00
Feb 28 10:37:00 guactest guacd[4519]: #011drawingFlags: 0x0E
Feb 28 10:37:00 guactest guacd[4519]: #011multipleRectangleSupport: 0x0001
Feb 28 10:37:00 guactest guacd[4519]: #011pad2OctetsB: 0x0000

 

...

 

Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: Receiving
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: BitmapCapabilitySet (length 24):
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011preferredBitsPerPixel: 0x0010
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011receive1BitPerPixel: 0x0001
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011receive4BitsPerPixel: 0x0001
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011receive8BitsPerPixel: 0x0001
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011desktopWidth: 0x0480
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011desktopHeight: 0x0360
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011pad2Octets: 0x0000
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011desktopResizeFlag: 0x0001
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011bitmapCompressionFlag: 0x0001
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011highColorFlags: 0x00
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011drawingFlags: 0x1E
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011multipleRectangleSupport: 0x0001
Feb 28 10:38:00 GD-UKN-RDE2-06 guacd[4519]: #011pad2OctetsB: 0x0000

```

 

is guacd ignoring the recieved BitmapCapabilitySet and failing to relay through the java app?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)