Repository navigation
Fix wrong portal assumtions about monitor position #151
Repos I am interested in contributing tohttps://github.com/hyprwm/xdg-desktop-portal-hyprland What I want to contribute right now
This seems wrong. It should be the screen's position in the desktop layout, in logical coordinates. Currently it's hardcoded and breaks some screenrecording software (my own is the client i've tested so far: https://github.com/faetalize/waytator) Why the above bug / feature specifically?For example, with DP-2 at Other portals do this - xpdh doesn't. Is that intended? If I'm not missing something, then it should be fixed. FIX HERE: hyprwm/xdg-desktop-portal-hyprland#462 I acknowledge that:
|
Replies: 2 comments 1 reply
|
Same bug here, just with a different client, in case another data point helps. Host is Omarchy 4.0.0.alpha / Hyprland 0.57.2 on Wayland, rustdesk 1.5.1-1, xdg-desktop-portal-hyprland 1.5.0, xdg-desktop-portal 1.22.1. Controller is Windows 11, also RustDesk 1.5.1. Layout is the same shape as yours: eDP-2 is disabled but still occupies 0,0, and HDMI-A-1 sits at 1920,0 (2560x1440, scale 1.25). That one is what gets shared. Symptom: the remote pointer is shifted right by exactly one monitor origin. It stops at about 75% of the width (1920/2560), the right quarter is unreachable, and a second stale cursor gets drawn somewhere. Turning off "show remote cursor" on the Windows side does nothing, and 1.5.3 behaves the same, so it's not the client drawing an extra cursor. RustDesk's server log on the host shows both coordinate spaces in one connection: Input is injected over the real layout range (1920..4480), while the rect handed to the client starts at 0. src/server/display_service.rs:872 takes the stream position as that rect's origin, and libs/scrap/src/wayland/pipewire.rs:712 defaults it to (0, 0), so whatever Start() reports is what the client will believe. |
|
welcome aboard! |

welcome aboard!