Hi, which version of freerdp do you use? Might be related to a bug already fixed if it is an older one.
The server OS and settings would also be very relevant. /gfx was introduced with windows 8 and nearly each version since has introduced a new mode (avc420, avc444, ...) By default avc444 is not turned on or some line idle setting server side might kick in. regards Armin P.s. Would suggest to not use the async options as they have been buggy and only work properly with certain preconditions applied. On 07/25/2018 12:34 PM, Michael Etscheid via FreeRDP-devel wrote: > Hello > > I have an old thin client with VIA900 and use an older thinstation version > with Linux kernel 3.2 as OS. > When I use freerdp with /rfx all is OK. But when I use the parameters /rfx > /gfx:AVC444, with WLOG_LEVEL=TRACE turned on, I can see that after a short > time no output appears via [com.freerdp.channels.rdpgfx.client]. If I move > the mouse, the data is processed on the rdpgfx channel. > Has anybody got any ideas? > > The +async-input etc switches did not help. The channel rdpsnd is processed > normally without getting stuck . > > I'm grateful for any clues > > Michael > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > FreeRDP-devel mailing list > FreeRDP-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freerdp-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
