http://bugs.winehq.org/show_bug.cgi?id=59822 --- Comment #2 from maxmeyer414@gmail.com --- More details: Bug 1 — Wine 9.22+ with yabridge 5.1.1: Plugin UI frozen, clicks not received With Wine Staging 11.0 (system) and yabridge 5.1.1, plugin UIs render visually but receive no mouse input whatsoever. The UI is completely frozen — knobs, buttons and dropdowns cannot be interacted with. Automation parameters can still be changed via the DAW, confirming the plugin loads correctly but the GUI input layer is broken. Enabling virtual desktop emulation in winecfg restores click functionality, but causes dropdowns to open inside the virtual desktop window rather than the plugin UI, and a floating virtual desktop window persists on screen. Wine 9.21 exhibits identical behaviour — the virtual desktop workaround is required there as well, suggesting the issue may not be purely the 9.22 regression but also related to the KDE/X11 environment. Bug 2 — Wine 10.0 (patched) with new-wine10-embedding yabridge: Cursor disappears behind plugin window After applying the regression patch (removing if (data->wm_state_serial) return 0 lines from dlls/winex11.drv/window.c) and building yabridge from the new-wine10-embedding branch, plugin UIs are no longer frozen. However, the mouse cursor visually disappears when hovering over the plugin window. The cursor is hidden behind the plugin window and clicks do not register on the plugin UI. This appears to be the cursor offset issue documented in issue #409, not yet resolved for Reaper on KDE/X11 (nor Wayland). What was expected: Plugin UIs should receive mouse input correctly without requiring virtual desktop emulation. -- 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.