Incorrect mouse cursor offset with Wine 9.22+

[cobe571]

Thanks for giving yabridge a shot!

• I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

Hello everyone,
Today I update my Debian 12 (bookworm) with yabridge 5.1.1 to Kernel Linux 6.1.0-28-rt-amd64 x86_64 and Wine Staging 9.22

Just to be sure everything works fine in the end I follow these steps:

I delete the file:
/home/patrizio/.config/yabridgectl/config.toml

And the two directories:
/home/patrizio/.vst/yabridge/
/home/patrizio/.vst3/yabridge/

As usual I gave the commands:

:~$ /home/patrizio/.local/share/yabridge/yabridgectl add /home/patrizio/.vst/

:~$ /home/patrizio/.local/share/yabridge/yabridgectl add "$HOME/.wine/drive_c/Program Files/Common Files/VST3"

:~$ /home/patrizio/.local/share/yabridge/yabridgectl sync

Everything works fine! But...

All of the programs I use i.e. Carla Audio Plugin Host; Reaper and Ardour DAW recognize the plugins but when I open it in most cases they have a really strange behavior. Most of them don't show their GUI with controls and many others don't works at all.

I downgrade winehq-staging to version 9.21 and now everything works perfectly.

Note to remember. To downgrade Wine Staging version, all the files needed for the downgrade must be listed in the installation command:

:~$ sudo apt install winehq-staging=9.21~bookworm-1 wine-staging=9.21~bookworm-1 wine-staging-amd64=9.21~bookworm-1 wine-staging-i386=9.21~bookworm-1

Until it will be fixed I marked Wine Staging as blocked with:

:~$ sudo apt-mark hold winehq-staging

**

Hope it will be fixed very soon, cause I really like yabridge and I appreciate so very much I can finally use a full set of windows plugins into my Linux computers.

Thanks for the effort and please keep up with the good job!

~Patrizio.

What did you expect to happen?

That everything works as expected

What actually happened?

Loading plugins was a faliure: No GUI and most of the plugins not working at all

Operating system

Debian GNU/Linux 12 (bookworm)

How did you install yabridge?

github

yabridge version

5.1.1

yabridgectl version

5.1.1

Wine version

9.22

Plugin

Almost all of them

Plugin type

both VST2 and VST3

Plugin architecture

64-bit

Host

Carla; Reaper; Ardour 7

Desktop environment or WM

XFCE 4.18

GPU model

AMD PALM

GPU drivers and kernel

Mesa 22.3.6 on Kernel 6.1.0-28-rt-amd64

Debug log

No response

Anything else?

No response

[Abso793]

Hello. I have this problem too. With wine-staging 9.22 i can't interact with the gui of the plugins. I have seen people mention this issue on winehq forum and on reddit too.

[siborg]

I reverted to 9.19 and the issues were resolved so there must be some regression or incompatibility in wine 9.22. It happens every now and then. Very Best Regards, Szymon Kosecki

…

On Mon, 25 Nov 2024 at 19:08, Abso793 ***@***.***> wrote: Hello. I have this problem too. With wine-staging 9.22 i can't interact with the gui of the plugins. I have seen people mention this issue on winehq forum and on reddit too. — Reply to this email directly, view it on GitHub <#382 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ6NUWJ4GMRMKYSKCLOG732CNYRBAVCNFSM6AAAAABSOTYP6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYHAZDCOJXGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[pablo-888]

Same. I thought it was a wine-tkg problem so I switched to vanilla but then I noticed Arch was actually a couple of wine versions behind so that explains it. I couldn't interact with Melodyne.

[sandycorzeta]

This perhaps due Wine in 9.22 going into Wayland by default.
https://www.phoronix.com/news/Wine-9.22-Released

I have the same problem, but instead i can interact with the VST with wrong scaling? (i guess)
i use 1360x768 on my native resolution, but the VST seems going into over more than my native resolution in 9.22. So i have the button pressed wrong location.

9.21 doesn't have this problem.

[sandycorzeta]

Here are some video preview of what happened in my computer.
It looks like the window coordinate initialization is not properly configured when the plugin being launched.
Perhaps almost looks like the same bug from #368 .

My system is Fedora 41 using Wine 9.22 copr build from patrickl

2024-11-26.14-48-38.mp4

[robbert-vdh]

Thanks for letting me know about this! I'll probably need to dive into what actually changed between Wine 9.21 and 9.22 to figure out what's happening here. I'll try to find time for that this weekend. For now you'll have to downgrade to an earlier version of Wine.

This perhaps due Wine in 9.22 going into Wayland by default.

yabridge has been unsetting WAYLAND_DISPLAY since early 2023 in anticipation for that on its own should not be causing any problems

I have the same problem, but instead i can interact with the VST with wrong scaling? (i guess)
i use 1360x768 on my native resolution, but the VST seems going into over more than my native resolution in 9.22. So i have the button pressed wrong location.

Are you using yabridge 5.1.1? Wine 9.17 changed how it handles DPI scaling, which did cause issues like this. Yabridge 5.1.1 should scale fine with all current Wine versions.

[bsedin]

I have same problem on wine 9.22, downgrading wine to 9.21 fixes it.
yabridge compiled from a82bd51 (with DPI scaling fix). I will try to test on latest master branch

[sandycorzeta]

Are you using yabridge 5.1.1? Wine 9.17 changed how it handles DPI scaling, which did cause issues like this. Yabridge 5.1.1 should scale fine with all current Wine versions.

Yes i'm using yabridge 5.1.1 compiled from patrickl COPR when im testing this.

[ArtikusHG]

For me, this also affects older wine versions. This started happening to me when I upgraded to 9.20. Downgrading to 9.17 only partially fixed it - on 9.20 I couldn't use the mouse to interact with the GUI at all, on 9.17 it would work on some plugins, but not others (Melodyne was still broken). The only version that works without issues currently for me is 9.21 (even with Melodyne).

Btw this is on Arch running the official packages for both yabridge and wine (switched to wine-staging to install 9.21 though). Don't think it matters, but just in case, my DAW is Reaper, my DE is GNOME on Wayland and I'm running it all through distrobox on Fedora Silverblue.

[Nekkowe]

I'm experiencing the same problem.
Linux Mint, X11, Reaper, wine-devel 9.22, yabridgectl 5.1.1
The plugin UIs do not react to the mouse in any way whatsoever, every one I've tried appears completely frozen.

Downgrading to 9.21 fixed it for me too.

[robbert-vdh]

I don't know if I still have the time to cook up a yabridge-side workaround for this today (and if that's possible to do in a reasonably sane manner) but for context, this is the Wine commit that introduced this issue's specific regression where GUI interaction just no longer works:

Patch: https://gitlab.winehq.org/wine/wine/-/merge_requests/6569
Specific commit causing the problem (through interaction with an earlier commit): wine-mirror/wine@d8b5a3a

The ConfigureNotify events sent by yabridge are being ignored because of those new checks. These events are what tells Wine where on the screen the window actually is. You'll notice that if you move a plugin window around to align with the very top left corner of your screen, mouse interaction still works as expected with Wine 9.22. The same PR added the following line, which causes that wm_state_serial flag to no longer be cleared, causing the problem:

https://github.com/robbert-vdh/wine/blob/d8b5a3ae129e0971e71fcf6e95387d8d1e35e646/dlls/winex11.drv/window.c#L1442-L1443

[PennRobotics]

Because the problem is already bisected, I imagine a fix is coming in the next release. Nonetheless, Fedora users can use:

sudo dnf install --allow-downgrade winehq-staging-9.21
sudo dnf versionlock add winehq-staging

[chmaha]

Because the problem is already bisected, I imagine a fix is coming in the next release. Nonetheless, Fedora users can use:

sudo dnf install --allow-downgrade winehq-staging-9.21
sudo dnf versionlock add winehq-staging

Or alternatively just use the official Fedora 41 repo and install wine 9.15 which is apparently based off wine-staging.

[Skygge666]

Side question about the Wayland: Is there Wayland support planned for Yabridge? I wonder if this could make the proper plugin GUI available in Presonus Studio One.... Thanks!

[RustoMCSpit]

same here Bitwig 5.2.7 linux mint .debian

[0CCULTIST]

Still issues after Wine 10. For lazy people on Debian Bookworm:

sudo apt install --allow-downgrades winehq-staging=9.21~bookworm-1 wine-staging=9.21~bookworm-1 wine-staging-amd64=9.21~bookworm-1 wine-staging-i386=9.21~bookworm-1 && sudo apt-mark hold winehq-staging wine-staging wine-staging-amd64 wine-staging-i386

Replace "hold" with "unhold" when (or even IF at this point) WINE fixes this

9.21 is the last working version.

[RustoMCSpit]

i think this is possibly related to a much older bug report made about neuralnote running through yabridge, not certain however https://bugs.winehq.org/show_bug.cgi?id=56774

[Lairizzle]

Confirmed same issue and downgrade to 9.21 and a reboot fixed it for me.

[cnschn]

@robbert-vdh any ideas how much effort it would be to work around this from the yabridge side? I'd prefer not to downgrade wine, and while moving all plugin windows to 0,0 works for now it's not exactly convenient 😄

[robbert-vdh]

@cnschn That probably won't possible do to in a way that keeps the old behavior, and that won't break immediately again after the next Wine release. I briefly checked if I could get something to work by moving the window's position around and then compensating with negative translations but that didn't really work and is super janky.

I don't think the Wine people are going to change something on their side that would make this work again anytime soon though. Maybe they'll accept a patch from me that would make this work properly without any hacks, but I currently also don't really have the time to work on that.

[cnschn]

That's unfortunate, but understandable.

I really don't want to downgrade/pin wine to an older version, does anyone have any recommendations on how to manage prefixes using non-system versions of wine (on arch in my case)? I'm using Lutris for some games/applications already, maybe setting up a fixed version prefix for VSTs using that could be an option?

[cdunford]

Experiencing same issue on arch with 9.22 - does anyone know if there is an open issue in wine to address this?

[siborg]

It is a known issue with 9.22 please downgrade to 9.21 - afaik no fix in wine for this. @robbert-vdh/yabridge ***@***.***> was trying to get a workaround in place but if I remember correctly this is WiP at best - due to lack of time... Very Best Regards, Szymon Kosecki

…

On Sun, 22 Dec 2024 at 13:07, Craig Dunford ***@***.***> wrote: Experiencing same issue on arch with 9.22 - does anyone know if there is an open issue in wine to address this? — Reply to this email directly, view it on GitHub <#382 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ6NUQZCOEHAQMQSY5QYZT2G22QZAVCNFSM6AAAAABSOTYP6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQ2TANZTHE> . You are receiving this because you commented.Message ID: ***@***.***>

[cdunford]

Yeah I'll see about downgrading - that's always a bit of a headache on arch. Would be stellar if someone was able to fix this at some point.

[siborg]

you can probably go to /var/cache/pacman/pkg folder and install older package from there if it has not been emptied by yourself already. Very Best Regards, Szymon Kosecki

…

On Sun, 22 Dec 2024 at 15:08, Craig Dunford ***@***.***> wrote: Yeah I'll see about downgrading - that's always a bit of a headache on arch. Would be stellar if someone was able to fix this at some point. — Reply to this email directly, view it on GitHub <#382 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ6NUQ4NBS43MVFXM74YO32G3IWXAVCNFSM6AAAAABSOTYP6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQ4DMNRWGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[siborg]

Ah, and do not forget to mask wine in /etc/pacman.conf with Ignore-pkg = wine . you can google doing it for just a specific version if you want. Very Best Regards, Szymon Kosecki

…

On Sun, 22 Dec 2024 at 15:38, Szymon Kosecki ***@***.***> wrote: you can probably go to /var/cache/pacman/pkg folder and install older package from there if it has not been emptied by yourself already. Very Best Regards, Szymon Kosecki On Sun, 22 Dec 2024 at 15:08, Craig Dunford ***@***.***> wrote: > Yeah I'll see about downgrading - that's always a bit of a headache on > arch. Would be stellar if someone was able to fix this at some point. > > — > Reply to this email directly, view it on GitHub > <#382 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAQ6NUQ4NBS43MVFXM74YO32G3IWXAVCNFSM6AAAAABSOTYP6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQ4DMNRWGQ> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

[Lord-Formaldahyde-Brick]

I think this problem with 9.22 is wider than just yabridge. Carla fails too plus the plugins in Photoshop CS2 (which was the last Adobe product I ever bought...think on Adobe! ) All fail to respond to mouse, or at least not know the coordinates of the pointer.

[rncar]

Just update to Wine 10.1-1 in Arch Linux, not fixed yet.

[gearcoded]

@rncar,
I think if the issue occurs in yabridge (even though because the wine team made some changes), updating Wine won't help.

---

I decided to downgrade to wine-stable 9.0, and it seems to be working very well.
So, first I downloaded these packages:

• wine-stable
• wine-stable-amd64
• wine-stable-dev:i386
• wine-stable-i386:i386
• winehq-stable

from this link:
https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/main/

And installed them this way:

cd wine_9.0_bak
sudo dpkg -i *.deb

After that, I locked the packages from update:

sudo apt-mark hold wine-stable wine-stable-amd64 wine-stable-dev:i386 wine-stable-i386:i386 winehq-stable

After that, everything is working correctly as before.

[robbert-vdh]

Maybe it is possible to add some hack to yabridge if it detects the specific wine versions (like 9.22-10.0)?

@gearcoded There's sadly just not a clean way to get this to work again without it potentially immediately breaking again in the next biweekly Wine release. I think the way forwards would be to have Wine natively handle coordinates correctly even when its X11 windows are reparented (which like it previously did with the XEmbed support, which I also couldn't get to work again last time I tried it). That way yabridge no longer needs to do any hacky things to get the coordinates to line up, and the general behavior should also improve (e.g. dragging windows off screen in the top left corner has always been broken). But I don't think anyone from the Wine team would work on this, and I also just haven't had the time to look into it either.

Aside: With the general community moving toward Wayland (some more reluctantly than others) is there some merit in figuring out how yabridge should work without X11 in the distant future?

@PennRobotics It can't. At least, not without yabridge implementing its own Wayland compositor, because plugin APIs will still use reparented X11 windows for plugin GUIs on Linux for the foreseeable future. The story for embedding GUIs on Wayland is still not quite fleshed out, so first that would need to happen, then the plugin APIs need to have first class support for Wayland native GUIs, and then all of the DAWs would need to be updated to support that.

[S0yKaf]

I have same mouse shifting problem on Endeavour OS, I fixed it by downgrading from 9.22 to 9.21:

wget https://archive.archlinux.org/packages/w/wine-staging/wine-staging-9.21-1-x86_64.pkg.tar.zst
sudo pacman -U wine-staging-9.21-1-x86_64.pkg.tar.zst

This worked fine on arch for me. so good workaround in the meantime.

[KingKrouch]

So I'm using NixOS, and I happen to notice that (at least on KDE Plasma Wayland) that there's no mouse input inside of VST plugins. Is there a good fix for this? The only way I was able to pass activation in Serum was to open bitwig-studio through Gamescope.

[PennRobotics]

I'm not so familiar with the XCB terminology/API. Is there any significance to the XCB_MAP_NOTIFY and XCB_UNMAP_WINDOW events? These are passed to handle_x11_events, XCB_MAP_NOTIFY a few times after opening a plugin and then seemingly one XCB_UNMAP_WINDOW event after each button click (although never immediately after; rather, after the graphics invalidation and other click-related changes).

What's clear is that X11DRV_ButtonPress (actually event:call_event_handler) is the first sign of a button click in the log, and this function is getting the correct coordinate (cursor position w.r.t. plugin origin), and then cursor:map_event_coords is moving the event almost immediately away so that WM_NCHITTEST gets the wrong coords (lp includes the offset between the desktop and plugin window) and then returns 0 and is, from that point, ignored by the plugin window.

In fact, the only debug statement from the editor that happens during a button click is that ignored unmap event. All of the other debug log output comes from Wine.

I wasn't able to figure out how to load yabridge symbols into winedbg/gdb while attaching to a running plugin, so I couldn't actually connect a debugger. But, I have the next best thing: compile winex11.drv with a shedload of printf statements. I'll see if I can dump all of the variables involved with map_event_coords, compare to the changes from 9.22 and the patch a few users have recommended, maybe something stands out as faulty logic? Or, in the extreme case, Wine is convinced to add a flag for this use case?

[bandithedoge]

So I'm using NixOS, and I happen to notice that (at least on KDE Plasma Wayland) that there's no mouse input inside of VST plugins. Is there a good fix for this? The only way I was able to pass activation in Serum was to open bitwig-studio through Gamescope.

@KingKrouch Does this only happen with Wine 9.22+? Otherwise it's probably unrelated to this issue.

If you're experiencing windowing jank on Wayland you can try running Bitwig through another compositor like labwc (see Supreeeme/xwayland-satellite#32 (comment)),

[KingKrouch]

So I'm using NixOS, and I happen to notice that (at least on KDE Plasma Wayland) that there's no mouse input inside of VST plugins. Is there a good fix for this? The only way I was able to pass activation in Serum was to open bitwig-studio through Gamescope.

@KingKrouch Does this only happen with Wine 9.22+? Otherwise it's probably unrelated to this issue.

If you're experiencing windowing jank on Wayland you can try running Bitwig through another compositor like labwc (see Supreeeme/xwayland-satellite#32 (comment)),

I believe I'm using the latest version of WINE on Nix's Unstable repository, yes.

According to that, I'm on Version 10.

[olly1240]

So I'm using NixOS, and I happen to notice that (at least on KDE Plasma Wayland) that there's no mouse input inside of VST plugins. Is there a good fix for this? The only way I was able to pass activation in Serum was to open bitwig-studio through Gamescope.

@KingKrouch Does this only happen with Wine 9.22+? Otherwise it's probably unrelated to this issue.

If you're experiencing windowing jank on Wayland you can try running Bitwig through another compositor like labwc (see Supreeeme/xwayland-satellite#32 (comment)),

I believe I'm using the latest version of WINE on Nix's Unstable repository, yes.

According to that, I'm on Version 10.

That is the regression introduced by wine discussed here, if you move the vst window to the top left of the screen you should notice that it becomes interactable. The current solutions are: either downgrade wine to 9.21 or patch wine to restore the previous behavior

[David-Else]

I am trying to download the current Debian Trixie Wine 9 version so I can use it when I format the computer and reinstall the OS. I am pretty sure it will be updated to 10 soon and will have this bug. I have not had the opportunity to try it yet, but I think this is the solution. If anyone @gearcoded thinks this is wrong please tell me!

I downloaded the files I think I need with apt download:

and hope the following will work:

sudo apt install ./libwine_9.0~repack-7_amd64.deb ./wine64_9.0~repack-7_amd64.deb ./wine_9.0~repack-7_all.deb 
sudo apt-mark hold libwine wine64 wine

The theory is that they are in the right order so the dependencies will be satisfied by the previous one so it won't download the new dependencies for version 10 that will be available.

apt-cache depends wine  
wine
 |Depends: wine64
  Depends: <wine32>
 |Depends: wine64
  Depends: <wine32>
  Breaks: libwine
  Breaks: <wine-stable>
  Replaces: libwine
  Replaces: <wine-stable>

$ apt-cache depends wine64
wine64
  Depends: libc6
  Depends: libwine

$ apt-cache depends libwine
libwine
  Depends: libc6
  Depends: libfontconfig1
  Depends: libfreetype6
  Depends: libasound2t64
  Depends: libcapi20-3t64
  Depends: libglib2.0-0t64
  Depends: libgphoto2-6t64
  Depends: libgphoto2-port12t64
  Depends: libgstreamer-plugins-base1.0-0
  Depends: libgstreamer1.0-0
  Depends: libpcap0.8t64
  Depends: libpcsclite1
  Depends: libpulse0
  Depends: libudev1
  Depends: libunwind8
  Depends: libusb-1.0-0
  Depends: libwayland-client0
  Depends: libx11-6
  Depends: libxext6
  Depends: libxkbcommon0
  Depends: libxkbregistry0
 |Depends: ocl-icd-libopencl1
  Depends: <libopencl1>
    ocl-icd-libopencl1
 |Depends: ocl-icd-libopencl1
  Depends: <libopencl-1.2-1>
    ocl-icd-libopencl1
  Depends: libz-mingw-w64
  Breaks: wine
  Breaks: <wine32>
  Breaks: wine64
  Replaces: wine
  Replaces: <wine32>
  Replaces: wine64

I can't seem to download wine32, but I don't think I need it as I use all 64bit plugins:

wine32
State: not a real package (virtual)
Notice: Can't select candidate version from package wine32 as it has no candidate
Notice: Can't select versions from package 'wine32' as it is purely virtual
Notice: No packages found

[gearcoded]

@David-Else, if you downloaded the packages from another source, I cannot suggest which ones you need.
But I prefer the Winehq version as it is an official version. So, if I had Debian Trixie, I would go there:
https://dl.winehq.org/wine-builds/debian/dists/trixie/main/binary-amd64/

And then I would download these packages:

• winehq-stable_9.0.0.0~trixie-1_amd64.deb
• wine-stable-amd64_9.0.0.0~trixie-1_amd64.deb
• wine-stable_9.0.0.0~trixie-1_amd64.deb

If you have the working system (regardless of the Debian version), you can check the installed packages and save the names. To make it work in Debian 13, you just need to install the same packages for that version.

[mekosmowski]

Would someone please provide directions how to install the specific 9.21 in Ubuntu? I'm too inexperienced with apt.

I tried apt install wine-staging=9.21-noble-1, but it says it wants to install 10.1 instead.

[gearcoded]

@mekosmowski, have you tried installing the stable version? staging is an experimental branch, where you get newer features at the cost of stability. And I think when staging is installed, it always tries to get the latest version.

[dmotte]

First of all, thank you so much @robbert-vdh for providing this amazing piece of software!

I also experience this issue. My setup: Debian 12 (bookworm), Wine 10.0 (stable) installed from the official WineHQ repositories, yabridge 5.1.1, REAPER v7.33/linux-x86_64.

The mouse position is shifted by the position of the VST window, so it gets more usable if I move the VST window in the upper left corner of the screen.

Also, I noticed that using REAPER for Windows directly inside Wine (without yabridge) doesn't have this issue.

I will try to downgrade to Wine 9.21 too :)

[Trichiurus-lepturus]

The same mouse offset problem here when trying to load:
x64 vst3 or x64 clap plugins in
Bitwig 5.3.1 (alien deb2rpm), using
yabridge 5.1.1 which is installed with zypper, in
both x11 session and wayland session,
KDE Plasma 6.3.1,
openSUSE Tumbleweed. The default wine version for Tumbleweed is now
wine 10.0, but
the mouse offset problem remains. I'll now try to
downgrade to Wine 9.21.

[felix-hilden]

Hiya all, we've established that the issue is in Wine 9.22+, so adding more me-toos doesn't add much value for the people who are following this issue to know if a permanent solution is developed. Please try downgrading first before posting, and if it doesn't help, that would be quite interesting to know! 🙏

[PennRobotics]

For me, the current revision of Wine built from source plus MR 7429 gets rid of the mouse click offset (aka fixes this issue) although on my development laptop, I don't have a VST with menus to test if those also show up in the right place (at the cursor).

Anyone keen on building and testing to confirm this MR works or not (optionally, if it shows context menus correctly; and also does not break your other WINE programs)?

[PennRobotics]

Ah, drat! Valhalla does have a menu (when you click presets) and it does always show up in the same incorrect place no matter where the program window is, so context menus are not fixed. I'm unconvinced that's the same bug as the mouse offset.

[tetebueno]

Would someone please provide directions how to install the specific 9.21 in Ubuntu? I'm too inexperienced with apt.

I tried apt install wine-staging=9.21-noble-1, but it says it wants to install 10.1 instead.

@mekosmowski, I pulled it off on an Ubuntu 22.04 with the following downgrade:

$ sudo apt install wine-staging=9.21~jammy-1 winehq-staging=9.21~jammy-1 wine-staging-i386=9.21~jammy-1 wine-staging-amd64=9.21~jammy-1

[PennRobotics]

It would appear the issue is in the process of being solved. The preliminary patch offered in the bug report does not solve it entirely - context menus will still be positioned to absolute coordinates but that's bearable since that's at least on-screen I managed to make the patch work with wine-tkg on arch:

I just opened a bug about menus being offset:

https://bugs.winehq.org/show_bug.cgi?id=57886

[PennRobotics]

For anyone not following the latest pull request, mouse positioning now (after the merge) works from 9.22 to 10.2.

If you're impatient or want to help test your DAW, merge now (via gh pr checkout 405 --force or your preferred method) and build using the meson/ninja commands on the README.

Otherwise, wait for the merge to land in your package manager! ⏳ 🎁

[robbert-vdh]

I created a tracking issue for the changes from #405 here: #409

Please centralize the discussion around these new changes there!

[gaheldev]

Would someone please provide directions how to install the specific 9.21 in Ubuntu? I'm too inexperienced with apt.
I tried apt install wine-staging=9.21-noble-1, but it says it wants to install 10.1 instead.

@mekosmowski, I pulled it off on an Ubuntu 22.04 with the following downgrade:

$ sudo apt install wine-staging=9.21~jammy-1 winehq-staging=9.21~jammy-1 wine-staging-i386=9.21~jammy-1 wine-staging-amd64=9.21~jammy-1

Thank you, to anyone wondering here is the same for Ubuntu 24.10:

sudo apt install wine-staging=9.21~oracular-1 winehq-staging=9.21~oracular-1 wine-staging-i386=9.21~oracular-1 wine-staging-amd64=9.21~oracular-1

[bidinou]

Hi ! First, thanks so much to Robbert & everyone involved :)

I have a little question : am I supposed not to encounter the issue from Wine 10.3 forth, with the regular non-staging wine build and no dxvk ?

I updated my Manjaro from wine 10.2 to 10.3 (10.4 is coming) and still cannot register mouseclicks in my Arturia VSTs (from Bitwig, Ardour and QTractor).

Thanks so much for your amazing work, cannot believe I can run VSTs with a ridiculous latency on a 10 y.o PC through yabridge & Pipewire <3