[Bug 59492] New: Wine 11.3: Application renders partial viewport (Splashtop RMM)
http://bugs.winehq.org/show_bug.cgi?id=59492 Bug ID: 59492 Summary: Wine 11.3: Application renders partial viewport (Splashtop RMM) Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winex11.drv Assignee: wine-bugs@list.winehq.org Reporter: noah.bartlett@itguysteam.com Distribution: --- Created attachment 80495 --> http://bugs.winehq.org/attachment.cgi?id=80495 Image of what I see, remote desktop was 1080P rendered slightly below 1080P on my desktop When connecting to a remote desktop with a higher resolution than the local window (e.g. 4K remote on 1080p local), Splashtop renders only the top-left portion of the remote desktop that matches the local window resolution in pixels (1:1), leaving the remainder black. Reducing zoom makes the rendered area smaller rather than larger, suggesting the viewport is calculated as window_size × zoom_factor rather than scaling remote content to fit the window. The application works correctly on native Windows. Steps to reproduce: 1. Configure Splashtop RMM client to launch from atera/similar agent 2. Launch Splashtop RMM client under Wine and connect to a remote desktop with resolution higher than the local window 3. Observe that only the top-left portion renders; remainder is black Expected: Remote desktop content scales to fit the local window, renders full desktop I used this guide to get wine to launch splashtop from linux, but this did not modify wine (i think?) and this is occurring on both stable and staging versions of wine. https://community.syncromsp.com/t/splashtop-remote-access-from-linux-workaro... Additional testing — winewayland driver: Launching the application with DISPLAY= (unset) and WAYLAND_DISPLAY=wayland-0 to force Wine's native Wayland driver produced identical rendering behaviour, ruling out XRandR/Xinerama coordinate reporting as the direct cause. The partial viewport issue persists regardless of whether the X11 or Wayland graphics driver is used, suggesting the root cause is in a higher-level API (possibly GetSystemMetrics, GetMonitorInfo, or similar?) returning unexpected values on a multi-monitor system where one monitor has negative virtual screen coordinates. I am unsure if there are any logs that can help - but if you'd like to point me to what you need I'm happy to grab them and upload them. Also I'm kind of an idiot so I used claude to help generate a bug report as I don't want to waste anyone's time with a useless bug report that didn't have information that may be needed. I went over everything and it is correct, but any suggestions are claude conjecture so if they make no sense, I apologize. It's just a very strange issue. System info: Arch Linux x86_64 Kernel: 6.18.13-arch1-1 DE: Plasma 6.6.1/Wayland Host: Vostro 15 7510 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla