Dropdowns appear on wrong monitor

[dubsteptwo]

Compiled your fork today and now Serum works great! The only caveat so far is that context menus spawn on my second monitor no matter where the Serum window is.

https://github.com/user-attachments/assets/9344e9b0-8d5f-4a11-a72b-2f069fc2bea1
(Video shows me opening a bunch of context menus in Serum 2 running with d2d1-dcomp-11.0, they all appear on the dock on my second monitor; then I open pitchproof running with vanilla Wine 11.11, its context menus show up properly)

What I'm using:
Debian 13
Gnome (Wayland)
Bitwig 5.2
Yabridge "new-wine-10-embedding" from like the start of the year
wine-d2d1-dcomp-11.0

[giang17]

Can't reproduce this here: KDE on X11, dual monitor, Serum 2 via yabridge in both native
REAPER and Bitwig 6.0.6 (same yabridge base as you), on the same d2d1-dcomp-11.0 build.
Menus always open on Serum's monitor, including after moving the window.

Serum's menus are _NET_WM_WINDOW_TYPE_DIALOG with override-redirect = yes — Wine places
them at absolute coordinates itself and the WM is meant to leave them alone. That path is
identical to vanilla Wine in this fork (the fork's popup tweaks target owner-less
tool-window popups, not these), so it's unlikely to be the fork.

The differing variable is GNOME/Wayland vs. KDE/X11. Mutter is known to reposition
override-redirect windows onto a fixed output under XWayland on multi-monitor — which matches
your symptom. (pitchproof on vanilla isn't conclusive: different plugin and different Wine.)

Three tests would pin it down:

1. Log into "GNOME on Xorg" (gear on the login screen) and retry. Correct there = XWayland
   placement, not Wine.
2. Try with the second monitor disabled (single display). If the menus behave, it confirms
   this is multi-monitor output placement rather than menu positioning in general.
3. Optional, with a menu held open:

   for id in $(xwininfo -root -tree | grep -i yabridge | grep -oiP '0x[0-9a-f]{5,}'); do
     xprop -id $id _NET_WM_WINDOW_TYPE; xwininfo -id $id | grep -E 'Override Redirect|Absolute|Width|Height'
   done

   Expecting the same DIALOG + Override Redirect State: yes.

[giang17]

Update: I moved my own machine from KDE/X11 to GNOME on Wayland and still can't reproduce this. Serum 2 menus land correctly in every layout — plugin on either monitor, either one set as primary, and also with fractional scaling at 150%. So it's neither GNOME/Wayland/Mutter nor fractional scaling as such.

My setup: Ubuntu 24.04, GNOME/Mutter 46.2, NVIDIA 580, dual monitor (1080p + 1080p portrait).

The biggest remaining difference is the Mutter version — Debian 13 ships a much newer Mutter than my 46, so a placement change there is the leading theory. To narrow it down:

• gnome-shell --version
• monitor layout: resolutions, which is primary, scale % per monitor (especially if either is HiDPI/4K with fractional scaling — the one combo I can't mirror on 1080p)
• GPU + driver
• the xprop check from my first comment on the popup (expecting DIALOG + Override Redirect State: yes)

Screenshot (GNOME Wayland, dual monitor): Serum's OSC A menu opens in place on the Serum monitor, not on the other display.

[jake0x539]

Popping in to say there are definitely more variables at play, but I have no idea what they are - this happened to me for a few weeks on Linux Mint 22.3 w/ Cinnamon X11 (Ubuntu 24.04 base) AND on NixOS 25.11 w/ GNOME Wayland, and then went away. My main monitor is 1440p 180Hz and secondary monitor is 1080p 144Hz. No scaling. I've been using wine-d2d1-dcomp-11.0 and new-wine10-embedding at the start of April, and Giang's yabridge fork's fix/vst3-connect-on-gui-thread since it became available.

Serum 2 also wasn't the only plugin exhibiting this behavior, Kilohearts plugins would also open their menus, including preset browsers and stuff, on my second monitor sometimes.

I'm unsure why it stopped happening because I didn't switch my monitor setup. Could it be NVIDIA drivers? I have an RTX 3070 and was using the recommended NVIDIA proprietary drivers on Mint - I recall switching to latest at some point.

On NixOS 26.05 GNOME 50.1 Wayland, I'm using wine and yabridge in an Ubuntu 24.04 Distrobox, and it hasn't happened to me yet. My NVIDIA config is as follows - which should be the equivalent of running the latest driver on Mint:

hardware.nvidia = {
    open = true;
    package = config.boot.kernelPackages.nvidiaPackages.latest;
    modesetting.enable = true;
    powerManagement.enable = true;
};

My current NVIDIA driver version is 595.71.05.

I also recently tested uBlue Bazzite with the bazzite-dx-nvidia-gnome image with the same wine/yabridge/distrobox setup that I use on NixOS and I didn't experience this.

So, I think it's theoretically possible that it's a particular version of NVIDIA drivers that caused this, but I cannot say for sure.

[giang17]

Thanks @jake0x539 — very useful. Seeing it on Cinnamon/X11 and GNOME/Wayland, across
multiple plugins, and having it vanish after an NVIDIA driver update rules out Wayland/Mutter,
the fork, and the plugin. It points to a specific NVIDIA driver + multi-monitor combination
misreporting the output layout — which would explain both X11 and Wayland.

@dubsteptwo — what's your NVIDIA driver version? If you're not on the latest, updating is the
most likely fix (it resolved it for Jake, now on 595.71.05).

[dubsteptwo]

Sorry, should've probably said I was on Nvidia earlier.

My gnome-shell is 48.7
GPU is an RTX 4060, driver is 610.43

I can now confirm that this doesn't happen in any other environment for me other than Gnome/Wayland (the other environments being Gnome/X11, Openbox, Hyprland specifically), so maybe it could still be the override-redirect thing in my case? Which is really weird if Jake was also having this issue and you can't reproduce it at all.

More diagnostic stuff you asked for:

monitor layout: resolutions, which is primary, scale % per monitor (especially if either is HiDPI/4K with fractional scaling — the one combo I can't mirror on 1080p)

Both are 1080p 100% scale, the left one is primary

Here's the xprop output while having a Serum 2 context menu open on Gnome/Wayland:
xprop output.txt

I'll probably just switch to X11 or Hyprland for now, since it seems to work well enough there, because the virtual desktop just makes the context menus confine to the window it creates, which is worse imo

[jake0x539]

What an elusive bug. I might try installing Debian onto an external SSD later and see if I can’t reproduce it. Will report back. My working theory right now is that I misremembered having issues on Cinnamon X11 and that Mutter 48 specifically is cooked.

[giang17]

Conclusive now — and the xprop nails it. The menu is DIALOG + override-redirect (identical to what I see locally), but placed at x=1920, the origin of your second monitor, while Serum sits at x=365 on the first. Same Wine window; Mutter just puts it on the wrong output.

Your compositor matrix isolates it perfectly: only GNOME/Wayland breaks — GNOME/X11, Openbox and Hyprland are all fine. So it's neither Wayland in general (Hyprland is Wayland too) nor Wine — it's Mutter's multi-monitor popup placement. That's a long-standing weakness: GNOME/mutter#1783 (wrong-screen context menus in dual-monitor Wayland, open since Mutter 40, hits even native gedit/Firefox). #1783 is about native Wayland surfaces; yours is the XWayland flavour of the same problem.

Driver's ruled out — you're on the newest (610.43) and still hit it; Jake's "fix" was really his GNOME going 48→50.1. It looks version-dependent: 48 breaks, my 46.2 and Jake's 50.1 don't.

Nothing fixable on the Wine side, so X11 or Hyprland is the right call for now. If you'd like it fixed upstream, your xprop is excellent evidence for a Mutter report on the XWayland override-redirect angle (distinct from #1783's native-Wayland case).

[jake0x539]

Haven’t been able to reproduce it with dropdown menus, but I recently had the ”updating Wine configuration in $wineprefix” dialog pop up on my second monitor. Setup hasn’t changed, I haven’t even updated my system in this time.