You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2021/11/25 10:36:00 UTC

[jira] [Comment Edited] (GUACAMOLE-1464) Windows start menu accessible via client with RemoteApp connection

    [ https://issues.apache.org/jira/browse/GUACAMOLE-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449097#comment-17449097 ] 

Mike Jumper edited comment on GUACAMOLE-1464 at 11/25/21, 10:35 AM:
--------------------------------------------------------------------

Interesting.

For perspective, with respect to RemoteApp, the presence/absence of any particular application (including the start menu) is entirely on the Windows server. The server side of Guacamole sends the appropriate RDP mouse/key events in response to receiving those mouse/key events from the client side, and in return Windows sends a stream of graphical updates over RDP.

If you are seeing a start menu appear at any point, and this is not intentional behavior on Windows' behalf, this sounds like a possible bug in Windows' implementation of RemoteApp, perhaps due to Windows assuming that it will never receive mouse events for regions outside the visible area of an application window within the RemoteApp session.

As described above, we are essentially at the mercy of Windows with respect to what appears on the screen, but if this is indeed due to something like the assumption noted, maybe there is a way we can work around that.


was (Author: mike.jumper):
Interesting.

For perspective, with respect to RemoteApp, the presence/absence of any particular application (including the start menu) is entirely on the Windows server. The server side of Guacamole sends the appropriate RDP mouse/key events in response to receiving those mouse/key events from the client side, and in return Windows sends a stream of graphical updates over RDP.

If you are seeing a start menu appear at any point, and this is not intentional behavior on Windows' behalf, this sounds like a posible bug in Windows' implementation of RemoteApp, perhaps due to Windows assuming that it will never receive mouse events for regions outside the visible area of an application window within the RemoteApp session.

As described above, we are essentially at the mercy of Windows with respect to what appears on the screen, but if this is indeed due to something like the assumption noted, maybe there is a way we can work around that.

> Windows start menu accessible via client with RemoteApp connection
> ------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1464
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1464
>             Project: Guacamole
>          Issue Type: Bug
>          Components: RDP
>    Affects Versions: 1.3.0
>         Environment: Windows
>            Reporter: Matt Miller
>            Priority: Major
>
> We use a RemoteApp connection via RDP to access a program on a Windows server.
> Our program does not fill the whole client view.
> In the Guacamole client you can perform a left-mouse-button doubleclick on the black client screen outside of our program and then the Windows start menu appears. This is also possible by pressing the Windows key.
> While the Windows start menu is open you can no longer interact with our program.
> Closing the start menu is only possible by pressing the escape key.
> This leads to usability issues and accessing the Windows start menu or generally anything except the RemoteApp program shouldn't be possible anyway.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)