https://bugs.winehq.org/show_bug.cgi?id=57610
--- Comment #27 from Rémi Bernon rbernon@codeweavers.com --- Created attachment 77799 --> https://bugs.winehq.org/attachment.cgi?id=77799 Workaround
Oof... This is silly, it looks like that none of the monitors are primary in general but suddenly and only for one call, the second monitor briefly remembers that it is primary and that its crtc also moves to 0x0??
Anyway, lets try to workaround it instead, and use the monitor coordinates for the current display mode if they don't match. I don't see how this could fail now but I'm ready for anything at this point. I've also included some more traces, if you could make another log in any case. Thank you!