Re: RDP Black Square cursor QT Creator

[Mike Jumper <mi...@glyptodon.com>]

The issue you are seeing is a known issue in Chrome under Windows:

https://bugs.chromium.org/p/chromium/issues/detail?id=31463

When the mouse cursor is set to a transparent image, Chrome under Windows
will instead render that as a completely opaque black square. You are
encountering this when you press a key because the application within the
remote desktop is hiding the mouse cursor when you use the keyboard.

Michael Jumper
CEO, Lead Developer
Glyptodon Inc <https://enterprise.glyptodon.com/>.


On Sun, Jan 31, 2021 at 2:41 PM Adrian Owen <ad...@eesm.com> wrote:

> Hi Nick,
>
> All combinations of disable cache sadly made no difference with my 1.2
>
> disable-bitmap-caching true
>
> disable-offscreen-caching true
>
> disable-glyph-caching true
>
>
>
> Cursor keeps turning to Black square on arrow key down.  Adrian
>
>
>
>
>
> *From:* Nick Couchman [mailto:vnick@apache.org]
> *Sent:* 31 January 2021 21:57
> *To:* user@guacamole.apache.org
> *Subject:* Re: RDP Black Square cursor QT Creator
>
>
>
> On Sat, Jan 30, 2021 at 5:29 PM Adrian Owen <ad...@eesm.com> wrote:
>
> Hi, Guacamole 1.2 RDP Session->2019 Server.
>
>
>
> Visual Studio      – OK
>
> QT Creator (freeware)   – PROBLEM
>
>        On arrow key, cursor becomes Black square ?
>
>
>
>
>
> My suggestion would be to try various combinations of performance options
> to see if one or more of them result in the expected behavior. In
> particular, the Glyph Cache has been the subject of recent discussion, both
> here and with FreeRDP, in general, as the FreeRDP team considers it
> unreliable. This causes disconnects in certain versions of Windows, but I
> wouldn't be shocked if it causes issues like the one you're seeing. We've
> already introduced a change in the git code to forcibly disable it, but
> version 1.2 won't include this change, so you can try using the connection
> parameter to disable it. You might try the same with the other caching
> options if that doesn't work.
>
>
>
> -Nick
>

RE: RDP Black Square cursor QT Creator

[Adrian Owen <ad...@eesm.com>]

Thanks Mike.

From: Mike Jumper [mailto:mike.jumper@glyptodon.com]
Sent: 01 February 2021 23:43
To: user@guacamole.apache.org
Subject: Re: RDP Black Square cursor QT Creator

The issue you are seeing is a known issue in Chrome under Windows:

https://bugs.chromium.org/p/chromium/issues/detail?id=31463

When the mouse cursor is set to a transparent image, Chrome under Windows will instead render that as a completely opaque black square. You are encountering this when you press a key because the application within the remote desktop is hiding the mouse cursor when you use the keyboard.

Michael Jumper
CEO, Lead Developer
Glyptodon Inc<https://enterprise.glyptodon.com/>.


On Sun, Jan 31, 2021 at 2:41 PM Adrian Owen <ad...@eesm.com>> wrote:
Hi Nick,
All combinations of disable cache sadly made no difference with my 1.2
disable-bitmap-caching true
disable-offscreen-caching true
disable-glyph-caching true

Cursor keeps turning to Black square on arrow key down.  Adrian


From: Nick Couchman [mailto:vnick@apache.org<ma...@apache.org>]
Sent: 31 January 2021 21:57
To: user@guacamole.apache.org<ma...@guacamole.apache.org>
Subject: Re: RDP Black Square cursor QT Creator

On Sat, Jan 30, 2021 at 5:29 PM Adrian Owen <ad...@eesm.com>> wrote:

Hi, Guacamole 1.2 RDP Session->2019 Server.



Visual Studio      – OK

QT Creator (freeware)   – PROBLEM

       On arrow key, cursor becomes Black square ?



My suggestion would be to try various combinations of performance options to see if one or more of them result in the expected behavior. In particular, the Glyph Cache has been the subject of recent discussion, both here and with FreeRDP, in general, as the FreeRDP team considers it unreliable. This causes disconnects in certain versions of Windows, but I wouldn't be shocked if it causes issues like the one you're seeing. We've already introduced a change in the git code to forcibly disable it, but version 1.2 won't include this change, so you can try using the connection parameter to disable it. You might try the same with the other caching options if that doesn't work.

-Nick