https://bugs.kde.org/show_bug.cgi?id=525818
Bug ID: 525818
Summary: Video freezes after Windows RDP client is minimized or
client machine is locked, while input remains active
Classification: Plasma
Product: KRdp
Version First 6.7.4
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
SUMMARY
When connected to KRDP from Microsoft Remote Desktop on Windows, the session
works normally until the client stops displaying the remote output.
This happens when:
- the RDP client window is minimized, or
- the Windows client machine is locked while the RDP session is still open.
After restoring the RDP window or unlocking Windows, the last displayed frame
remains frozen.
Remote input is still active: mouse movement and clicks are still delivered to
the Fedora host even though the current desktop state is no longer visible.
Disconnecting and reconnecting the RDP session immediately restores video
output.
STEPS TO REPRODUCE
1. Start KRDP server normally on Fedora KDE Plasma / Wayland.
2. Connect from Windows using Microsoft Remote Desktop.
3. Verify that the remote desktop works normally.
4. Minimize the RDP client window.
5. Restore the RDP client window.
Alternatively:
4. Lock the Windows client machine while the RDP session is open.
5. Unlock Windows and return to the RDP session.
OBSERVED RESULT
The remote image remains frozen on the last frame.
Remote input is still active and actions are still sent to the Fedora host.
Disconnecting and reconnecting the RDP session restores video immediately.
Simply moving focus away from the RDP client, or placing another window in
front of it, does NOT reproduce the problem.
EXPECTED RESULT
The video stream should resume automatically when the RDP client becomes
visible again or after the Windows client machine is unlocked.
SOFTWARE/OS VERSIONS
Server:
Fedora 44 KDE Plasma / Wayland
KRDP tested with:
6.7.4-1.fc44
6.7.5-1.fc44
KWin:
6.7.5-1.fc44
Plasma Workspace:
6.7.5-1.fc44
KPipeWire:
6.7.5-1.fc44
Client:
Microsoft Remote Desktop on Windows
ADDITIONAL INFORMATION
During the failure, KRDP logs:
Cannot start recording on a stream without a node ID
KRDP 6.6.5 does not exhibit this specific video-freeze behavior on the same
machines.
Earlier 6.7.x versions had a separate connection/startup problem on this setup
where, after accepting the certificate, the connection would begin but the RDP
session failed to start correctly or the RDP client closed. That appears to be
a separate issue.
--
You are receiving this mail because:
You are watching all bug changes.
