https://bugs.winehq.org/show_bug.cgi?id=46309
--- Comment #22 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to Gabriel Ivăncescu from comment #21)
This bug was fixed only recently, the regression commit is far older, why would it be a regression of *this* bug in the first place? That's what I'm saying. It makes no sense. If there's a regression with the application itself it doesn't mean it goes into the same bug report. We separate bug reports for each specific problem, not per application.
Usually regressions have their own bug and in this case we have bug 50381 for that. It's not a duplicate because this bug is about it moving erratically *before* that regression commit. And that happens even on other WMs, like GNOME's Mutter, or Compiz. And that's exactly what the commit fixed and why this bug is fixed.
The regression is a *separate* bug and has nothing to do with it, even if the behavior is the same. As I said we already have a bug for the regression (bug 50381), please use that one for now. If it gets fixed and Winamp still has an issue on MATE, then please file a new regression bug because, as I said, it has nothing to do with this bug which existed before that commit, on other WMs, which *is* fixed.
I understand your reasoning, however with current wine.git (wine-6.5+) this bug is not fixed, behaviour of Winamp matches what is described in the first comment. Reverting c5ec1585f6e5211a2b63e3435748210552250534 does fix it. By all means this bug is not fixed, anyone is free to test it, and report back the results.