Hi Nick, Thnaks! It looks like it could be related. According to ms documentation: >>>The Stream Surface Bits Command is used to transport encoded bitmap data destined for a rectangular region of the primary drawing surface from an RDP server to an RDP client. >>> https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/b2218638-3cf9-4f2f-be61-b096ec3c8dc5
could be that guacamole is sending cmdType 0x0000 when it should be: 0x0006?? >>> cmdType (2 bytes): A 16-bit, unsigned integer. Surface Command type. This field MUST be set to CMDTYPE_STREAM_SURFACE_BITS (0x0006). anyway to change this vía configuration or "simple" patching so I can try it? thanks, Fernando El lun, 17 ene 2022 a las 17:51, Nick Couchman (<vn...@apache.org>) escribió: > On Fri, Jan 14, 2022 at 5:02 AM Fernando C. de Urien y Muñiz < > fur...@nts-solutions.com> wrote: > >> Hi again, >> I made more test. I wanted to be sure that the guacamole setup was >> correct so I tested guacd (1.3.0 and 1.4.0) in different environments. None >> of them is working when connecting to weston (black screen) >> >> >> - Docker image >> - Ubuntu 20.04 >> - Ubuntu 21 >> - Centos 8 >> >> All the scenarios lead to the same results: >> >> - guacamole to rdp servers as Win10 and Xrdp work >> - remmina, vinagre and other rdp clients on ubuntu/centos to weston >> work >> - guacamole to weston (weston on debian, ubuntu 21, ubuntu 20.04) the >> screen stays in "black" (mouse and keyboard are working) >> >> I strongly believe that is something very specific between guacd and >> weston. Can somebody help with this. >> >> > I just spun up a Fedora 35 system with weston and am seeing the same > behavior when connecting from Guacamole. I haven't tried all that much, > but, running weston via CLI I get a lot of the following messages: > > [10:23:51:539] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:577] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:617] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:769] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:769] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:795] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:795] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:795] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:867] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:868] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:893] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:893] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:893] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > [10:23:51:919] [3467:3467] [WARN][com.freerdp.core.surface] - > SURFACE_BITS_COMMAND->cmdType 0x0000 not allowed, correcting to 0x0006 > > Not entirely sure that's related, but seems like it could be. I haven't > done any debugging on the guacd side, either. > > -Nick >
