I was just looking at this JIRA issue yesterday - I will try to replicate this and see what I can figure out.
-Nick > On Aug 13, 2017, at 12:32, Mike Jumper <[email protected]> wrote: > > Hello all, > > There has been a long-outstanding issue in JIRA regarding RemoteApp which > I've been unable to find the time to investigate, and could use some > attention from a fresh pair of eyes: > > https://issues.apache.org/jira/browse/GUACAMOLE-125 > > The issue reported is that the screen size of the RemoteApp session appears > to persist at a lower resolution after reconnecting. Though the screen size > is initially set correctly, and reconnecting produces a Guacamole > connection with the correct size, RemoteApp windows are clipped within the > screen area of the previous connection. > > Since that reconnecting step guarantees that there is no shared state > between the Guacamole connections, I can think of at least the following > possibilities: > > 1) Windows itself was never designed to handle changes in client resolution > for a single RemoteApp session, or this is a bug which is generally not > encountered in practice (as the client resolution for a native client would > be the screen resolution, and the user would need to disconnect, change > their monitor settings, and reconnect for this to occur). > > 2) It is a bug in FreeRDP. > > 3) It is not a bug in FreeRDP, but there are some additional properties > which need to be set, functions which need to be called, or some other > undocumented magic which needs to be reverse-engineered from FreeRDP's X11 > client and added to Guacamole's implementation of the same. > > I have not been able to reproduce this yet myself, but it's clear that this > problem does occur, at least for some users. > > Any assistance in nailing this down so this issue can move forward would be > appreciated. > > Thanks, > > - Mike
