[ https://issues.apache.org/jira/browse/GUACAMOLE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Jumper reopened GUACAMOLE-1026: ------------------------------------ Welp, the fix we put in place (correcting the inverted logic) is only part of the story. The rest is that FreeRDP 3.x introduced support for RDP's "connection types" (the type of network between client and server), with the default being automatic detection. When automatic connection type detection is in use, the RDP server is required to ignore performance flags. >From the closed upstream issue, this is expected behavior and not a bug: >https://github.com/FreeRDP/FreeRDP/issues/11521 We need to take steps to restore the functionality of these performance flags, since they are otherwise broken. The conversation in the above issue suggest that we may be able to achieve this by explicitly selecting _any_ connection type, such as "LAN". > Add support for FreeRDP 3.0.0 > ----------------------------- > > Key: GUACAMOLE-1026 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1026 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, RDP > Reporter: Mike Jumper > Assignee: Alexander Leitner > Priority: Major > Fix For: 1.6.0 > > > The nightly CI build testing that guacamole-server builds against the FreeRDP > {{master}} branch started failing on 2020-04-10 due to the version bump to > 3.0.0. It's currently unclear whether the API has changed, as well. > The guacamole-server build should be adjusted such that it recognizes FreeRDP > 3.0.0. If further code changes are necessary for this to work, those changes > should probably also be made now before things get too hairy. -- This message was sent by Atlassian Jira (v8.20.10#820010)