https://bugs.kde.org/show_bug.cgi?id=518561
Bug ID: 518561
Summary: Cursor not visible in RDP clients that don't implement
TS_POINTER_PDU (RDVR, aRDP, Android clients)
Classification: Plasma
Product: KRdp
Version First 6.6.3
Reported In:
Platform: Other
OS: Unspecified
Status: REPORTED
Severity: critical
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
## Summary
krdpserver uses PipeWire ScreenCast with cursor_mode=Metadata.
The cursor is transmitted as RDP TS_POINTER_PDU (cursor shape packets).
Android RDP clients (tested: RDVRand aRDP on Meta Quest 3) do not implement
TS_POINTER_PDU and therefore show no cursor at all.
My guess is, that this is on many clients a problem, so it would be much better
to render it in the stream or at least provide an option to switch this
behaviour on.
It is not possible in any way to use kde / plasma and therefore linux in VR!
The video stream runs smoothly, but without cursor on the client... :(
## Expected behavior
Cursor should be visible for all RDP clients, not only windows remote desktop.
## Suggested fix
Use cursor_mode=Embedded in PipeWire ScreenCast request, so the cursor
is burned into the video frame and visible regardless of client
cursor shape support.
## Environment
- KDE Plasma 6.6.3 / CachyOS / Wayland
- krdpserver 6.6.3
- Client: RDVR (Meta Quest 3), Android platform
- GPU: AMD Radeon RX 6800 (radeonsi VA-API)
## Related
- RDPGFX_CAPVERSION_107 selected, AVC: true YUV420: true
- KWIN_FORCE_SW_CURSOR=1 has no effect (cursor still transmitted
as PDU, not embedded in stream)
--
You are receiving this mail because:
You are watching all bug changes.
