https://bugs.kde.org/show_bug.cgi?id=525818
--- Comment #3 from Nikolay Talev <[email protected]> --- Thanks for the response. I reproduced the issue again and captured the journal as requested. The RDP session was working normally. I then minimized the Microsoft Remote Desktop client on Windows and restored it. After restoring the client, the displayed image remained frozen on the last frame. Input was still active during the freeze. Mouse movement and clicks were still being transmitted to the Fedora host and actions continued to be executed, even though no new video frames were displayed. Disconnecting and reconnecting the RDP session immediately restored the video. The most relevant part of the log appears to be: Sep 17 08:58:02 fedora-laptop krdpserver[6390]: [libx264 @ 0x7f1294068a00] frame I:2 Avg QP: 0,00 size:502185 Sep 17 08:58:02 fedora-laptop krdpserver[6390]: [libx264 @ 0x7f1294068a00] frame P:126 Avg QP: 0,90 size: 36092 Sep 17 08:58:02 fedora-laptop krdpserver[6390]: [libx264 @ 0x7f1294068a00] kb/s:346999,59 Sep 17 08:58:07 fedora-laptop krdpserver[6390]: Cannot start recording on a stream without a node ID The full journal from the reproduction is attached. This issue is reproducible by minimizing the Windows RDP client and then restoring it. I have also reproduced the same behavior after locking and unlocking the Windows client machine while the RDP session remains open. Simply moving focus away from the RDP client or covering it with another window does not trigger the issue. KRDP 6.6.5 does not exhibit this specific video-freeze behavior on the same machines. -- You are receiving this mail because: You are watching all bug changes.
