Hi Armin, Many thanks for your points below.........particularly :
4. you can work around this by disabling AVC420, append '/network:auto /gfx` to fall back to Progressive codec...... I've just run the following command : xfreerdp ./RDS.rdp /u:<AD user> /p:<password> /gdi:hw /network:auto /gfx ........and already I've noticed a difference. Prior to today, if the connection dropped (the RDP session ended), I'd re-issue the command, and it would resurrect the RDP session (quite often without prompting me to enter any credentials), but I'd have to "minimise" then "maximise" (by right clicking on FreeRDP in my taskbar, to get the menu up) in order to get the RDP window to display. It never did that with FreeRDP version 2. I'll see how I go, and report back. If it works (as it used to do), I'll be *very* pleased :-) As a complete aside, I've looked at the man page for xfreerdp to see what the "/gdi" setting does. It states : "GDI rendering" ......which can be set to software (sw) or hardware (hw). Dare I ask what GDI rendering is? :-) Thanks again for all your help; most appreciated. Best Regards, Justin On Thu, 8 Aug 2024 at 17:31, akallabeth--- via FreeRDP-devel < freerdp-devel@lists.sourceforge.net> wrote: Ok, > > > that means: > > 1. OpenH264 is installed on your system. (this error code is only > returned if it is the real thing) > > 2. your server has some quite strange/awkward configuration. > > 3. your server sends invalid H264 data (might happen with some driver > combinations) > > 4. you can work around this by disabling AVC420, append '/network:auto > /gfx` to fall back to Progressive codec (that is what you get with > Fedoras FreeRDP2 as the openh264 support is quite new) > > > regards > > Armin > > On 08.08.24 17:29, Justin Eastham wrote: > > ........apologies, I clicked on the Send button too quick :-/ > > > > In response to your final point : > > > > *> the error should be preceded by warnings detailing which OpenH264 > > operation failed for which reason. (that would be the more interesting > > log entry........* > > > > It's just the two lines : > > > > [13:04:51:810] [2077:0000083f] [WARN][com.freerdp.codec] - > > [openh264_decompress]: DecodeFrame2 state: 0x20 > > [13:04:51:810] [2077:0000083f] [WARN][com.freerdp.gdi] - > > [gdi_SurfaceCommand_AVC420]: avc420_decompress failure: -2003, > > ignoring update. > > [13:04:51:838] [2077:0000083f] [WARN][com.freerdp.codec] - > > [openh264_decompress]: DecodeFrame2 state: 0x20 > > [13:04:51:839] [2077:0000083f] [WARN][com.freerdp.gdi] - > > [gdi_SurfaceCommand_AVC420]: avc420_decompress failure: -2003, > > ignoring update. > > [13:04:51:870] [2077:0000083f] [WARN][com.freerdp.codec] - > > [openh264_decompress]: DecodeFrame2 state: 0x20 > > [13:04:51:870] [2077:0000083f] [WARN][com.freerdp.gdi] - > > [gdi_SurfaceCommand_AVC420]: avc420_decompress failure: -2003, > > ignoring update. > > [13:04:51:900] [2077:0000083f] [WARN][com.freerdp.codec] - > > [openh264_decompress]: DecodeFrame2 state: 0x20 > > [13:04:51:900] [2077:0000083f] [WARN][com.freerdp.gdi] - > > [gdi_SurfaceCommand_AVC420]: avc420_decompress failure: -2003, > > ignoring update. > > [13:04:51:938] [2077:0000083f] [WARN][com.freerdp.codec] - > > [openh264_decompress]: DecodeFrame2 state: 0x20 > > [13:04:51:939] [2077:0000083f] [WARN][com.freerdp.gdi] - > > [gdi_SurfaceCommand_AVC420]: avc420_decompress failure: -2003, > > ignoring update. > > [13:04:51:962] [2077:0000083f] [WARN][com.freerdp.codec] - > > [openh264_decompress]: DecodeFrame2 state: 0x20 > > [13:04:51:962] [2077:0000083f] [WARN][com.freerdp.gdi] - > > [gdi_SurfaceCommand_AVC420]: avc420_decompress failure: -2003, > > ignoring update. > > [13:04:52:993] [2077:0000083f] [WARN][com.freerdp.codec] - > > [openh264_decompress]: DecodeFrame2 state: 0x20 > > [13:04:52:993] [2077:0000083f] [WARN][com.freerdp.gdi] - > > [gdi_SurfaceCommand_AVC420]: avc420_decompress failure: -2003, > > ignoring update. > > [13:04:52:027] [2077:0000083f] [WARN][com.freerdp.codec] - > > [openh264_decompress]: DecodeFrame2 state: 0x20 > > [13:04:52:028] [2077:0000083f] [WARN][com.freerdp.gdi] - > > [gdi_SurfaceCommand_AVC420]: avc420_decompress failure: -2003, > > ignoring update. > > > > ........hope it means more to you than it means to me :-) > > > > Thanks again, > > > > Justin > > > > > > On Wed, 7 Aug 2024 at 20:32, akallabeth--- via FreeRDP-devel > > <freerdp-devel@lists.sourceforge.net> wrote: > > > > Hi Justin, > > > > > > what command line do you use and what is your target RDP server OS? > > > > AVC420 should not be in use anymore as there were issues with that > > spec > > (it was replaced by AVC444 with systems newer than windows 8.1) > > > > > > anyway, the error should be preceded by warnings detailing which > > OpenH264 operation failed for which reason. (that would be the more > > interesting log entry, you posted the final 'something failed, look > > above' message) > > > > > > regards > > > > Armin > > > > On 07.08.24 17:40, Justin Eastham via FreeRDP-devel wrote: > > > Hi all, > > > > > > I've signed-up to this mailing list, in the hope that somebody > > can point me > > > in the right direction. > > > > > > Prompted by a SSD expiry, I carried out a fresh install of > > Fedora 40. I was > > > previously running Fedora 39.......and had no issues with FreeRDP. > > > > > > As you're no doubt aware, F39 shipped with FreeRDP v2 : > > > > > > at release : freerdp-2.11.2-1.fc39.x86_64.rpm > > > latest : freerdp-2.11.7-1.fc39.x86_64.rpm > > > > > > .....whereas F40 ships with v3 : > > > > > > at release : freerdp-3.4.0-1.fc40.x86_64.rpm > > > latest : freerdp-3.6.3-1.fc40.x86_64.rpm <--- what I > > currently > > > have installed. > > > > > > The problem I'm seeing is : > > > > > > "[WARN][com.freerdp.gdi] - [gdi_SurfaceCommand_AVC420]: > > avc420_decompress > > > failure: -2003, ignoring update." > > > > > > .......repeatedly; presumably every time it fails to render the > > screen > > > correctly, or it fails to draw a specific section of the screen. > > It's most > > > likely to occur whilst scrolling; for example in Outlook and Teams. > > > > > > Would this error be in some way related to connectivity issues? > > That said, > > > I never had this problem with Fedora 39 (FreeRDP v2). To > > eliminate WiFi, I > > > intend on hanging this laptop off the back of the WiFi router via > an > > > ethernet cable. > > > > > > I'm just wondering whether I can force the currently installed > > v3.6.3 to > > > fallback to v2 behaviour. Failing that, maybe I can download the > > source RPM > > > from the F39 repo, and build it on this F40 laptop......and then > > somehow > > > ring-fence it, so it doesn't get updated to version 3.x.y as > > part of a > > > wider system update. > > > > > > Googling the error, or even a portion of the error, doesn't seem > > to yield > > > much in the way of results :-/ > > > > > > I'd appreciate any help or guidance........even if it's just > > sending me off > > > to some web resource :-) > > > > > > Thanks in advance > > > > > > Justin > > > > > > _______________________________________________ > > > FreeRDP-devel mailing list > > > FreeRDP-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/freerdp-devel > > > > > > _______________________________________________ > > FreeRDP-devel mailing list > > FreeRDP-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freerdp-devel > > > _______________________________________________ > FreeRDP-devel mailing list > FreeRDP-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freerdp-devel > _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
