SUMMARY Krfb displays the cursor in the wrong place but the remote desktop's cursor is somewhere else when using UI Scaling. Once I reduced the UI Scaling to 100% it worked as expected STEPS TO REPRODUCE 1. Use a single monitor on KDE/Wayland 2. Given a base resolution of 2256x1504. Scale to 200% 3. connect with krfb OBSERVED RESULT Your mouse cursor is in the wrong location EXPECTED RESULT Mouse cursor should reflect it's actual location SOFTWARE/OS VERSIONS Windows client using RealVNC and TigerVNC Linux/KDE Plasma: KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I am using wayland as the compositor
Can reproduce this on Arch with 23.01.1.
(In reply to Oleksandr Natalenko from comment #1) > 23.01.1. 23.04.1 of course
Just wanted to mention that this issue is still present in Krfb 24.02.1, which makes it impossible to hit targets (e.g., buttons) with the cursor. Some additional information: The mouse cursor position on client and Krfb server matches correctly while the cursor is in the top left corner of the screen (origin point; 0,0) but drifts away the further the cursor moves from there. On 200% scaling, it is as if the client recognized the screen as having 4x as many pixels (e.g., 1920x1080 -> 3840x2160) with the same origin point of 0,0. E.g., if the cursor is, from the perspective of the client, positioned in the center of the screen, in actuality it is positioned in the absolute bottom right corner. FWIW, I have encountered the exact same issue with the nightly version of the Rustdesk Flatpak on Plasma, which also utilizes the "org.freedesktop.portal.RemoteDesktop" portal, so the issue might lie somewhere upstream. Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 30.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 980/PCIe/SSE2
Having the same problem, makes krfb unusable
Same here, Arch Linux with Wayland
*** Bug 471997 has been marked as a duplicate of this bug. ***