On Mon, Aug 14, 2017 at 10:39 AM, Nick Couchman < [email protected]> wrote:
> So, I finally got FreeRDP updated on my system from 1.0.2 to 1.1, and the > problem has disappeared, with one item worth noting... > When I left the system last night, I had left a session opened that I had > started with Guacamole and FreeRDP 1.0.2, and I had disconnected the > session. I upgraded FreeRDP and reconnected the session, and the issue was > there. I then killed the session off completely (send Ctrl-Alt-Delete to > the remote desktop server, Sign Off) and restarted it at various > resolutions, and the problem has completely disappeared. > This seems to indicate that the issue is something in how Guacamole + > FreeRDP establishes the initial session when you first connect to the > RemoteApp. So, it's either an issue in Guacamole with how Guacamole sets > up the RemoteApp connection with the older FreeRDP version, or it's an > issue in FreeRDP 1.0.2 with how FreeRDP establishes the RemoteApp session > that xfreerdp somehow works around. > I'll take a look at the xfreerdp code in the FreeRDP stable-1.0 branch and > see if there's anything obvious that stands out as to how the RemoteApp > sessions are initialized or maintained that might be missing from > Guacamole. Let me know if I can provide any more information. > Thanks, Nick - I hope something jumps out. The fact that the problem disappears after upgrading and doing a reboot dance is troubling. On one hand, it does suggest that there is something FreeRDP-specific about this, but if the problem does not occur when xfreerdp is used, then there must be some way for Guacamole to achieve the same. - Mike
