https://bugs.kde.org/show_bug.cgi?id=520260
Bug ID: 520260
Summary: Connections using the Microsoft RDP client on Android
(called "Windows App") often cause visual freezes
Classification: Plasma
Product: KRdp
Version First 6.6.90
Reported In:
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
DESCRIPTION
When I heard that KRdp now has an implementation of progressive encoding, I
decided to try compiling and running KRdp from git master (alongside KDE
Plasma, using the command `kde-builder plasma-desktop kscreen spectacle
plasma-keyboard plasma-systemmonitor xdg-desktop-portal-kde krdp` on Arch
Linux) to see if I can now connect to KRdp using Microsoft's official RDP
client on Android (now called the "Windows App") since it doesn't support H264
encoding.
Indeed, I am able to connect using that RDP client now, however I noticed that
it quite often results in the visuals being frozen but with input still
working, as in I can move the mouse, click on things and type stuff in the
client and have the host respond, but the picture on the client is still, aside
from the mouse cursor which I believe is rendered client side.
STEPS TO REPRODUCE
1. Run KRdp from git master (my compiled from source setup was at commit
8e1de600a6ea4fcb1662508626da2cf0499f9734)
2. Connect using the "Windows App" on Android
3. Try to use the system as normal through the RDP connection
OBSERVED RESULT
The screen on the client side freezes except the cursor
EXPECTED RESULT
The screen on the client should not freeze
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: Git master from kde-builder
KDE Frameworks Version: Git master from kde-builder
Qt Version: 6.11.1
Kernel Version: 7.0.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 18 × Intel® Core™ Ultra 5 125H
Memory: 32 GiB of RAM (30.8 GiB usable)
Graphics Processor: Intel® Arc (Mesa 26.0.6-arch1.1)
ADDITIONAL INFORMATION
In the logs, I can see a lot of "PipeWire frame did not contain usable image
data" messages from krdpserver, and when I try to disconnect from the client
side I see two more messages which say "pw_stream_set_active called from wrong
context, check thread and locking: Device or resource busy" and
"impl_ext_end_proxy called from wrong context, check thread and locking: Device
or resource busy". The system tray icon saying that KRdp is exercising remote
control privileges also stays even though I have disconnected, and if I try
stopping the KRdp service (either from the KCM or through systemctl directly) I
notice systemd takes some time to wait for KRdp to exit, but it eventually
gives up and issues a SIGKILL to KRdp.
If I just try disconnecting and reconnecting from the client side, it works
until it freezes again, and if I keep repeating that the system tray icons
saying that KRdp is exercising remote control privileges will start piling up
until I stop KRdp.
I tried another Android RDP client called aRDP, which has an option to enable
or disable H264 support, and if I disable that support I can sometimes
reproduce the same issue, but not consistently, while with the "Windows App" I
get the problem practically 100% of the time within a few seconds of moving
things around on the screen.
I also tried the KDE Linux live image named "kde-linux_202605160254.raw" from a
USB stick, and it behaves the same as my compiled from source setup.
--
You are receiving this mail because:
You are watching all bug changes.
