https://bugs.winehq.org/show_bug.cgi?id=46309
--- Comment #23 from Gabriel Ivăncescu gabrielopcode@gmail.com --- Well the bug itself is fixed. The application is not and has a regression; but like I said we separate bug reports per problem, not per application.
Obviously what the regression triggers is a completely separate thing from the fix in Rémi's commit. In short: it's a separate issue, and has its own bug report.
Just because the outcome is the same doesn't mean it's the same underlying problem.
For example an application could crash on launch due to many different issues. If one of them is fixed, the bug report gets resolved, even if it still crashes due to something else or a regression. Those go into a separate bug report.
In this case, Winamp's positioning is erratic due to different underlying issues. The one that this bug refers to is fixed.
But anyway, what good would it make to keep this bug open when we already have a bug tracking the regression?
You can't simply mark it as a duplicate, since the other bug is specifically about the regression, and *not* about the bug *before* that commit in the first place. Neither is it about other WMs. This bug *was* affecting other WMs as well. So it's obviously not a duplicate and it's about a different underlying cause/problem.