[Bug 46309] Winamp with Classic Skin "jumps randomly" when moved

[WineHQ Bugzilla]

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

--- Comment #21 from Gabriel Ivăncescu <gabrielopcode at gmail.com> ---
(In reply to Dmitry Timoshkov from comment #20)
> (In reply to Gabriel Ivăncescu from comment #19)
> > I never said that regression is not real. But this bug is *not* about Winamp
> > being unable to move, it's about it moving erratically when moved.
> 
> This is exactly what happens. Feel free to test it on your own.
> 
> > We
> > already have Bug 50381 about this regression, and I made a note about Winamp
> > there with a download link.
> > 
> > Is there a reason you don't want to use Bug 50381 for this regression? If
> > not, please close this bug because it's about an entirely different issue.
> 
> How would you propose resolving this bug? It's clearly not fixed, and this
> is a regression. So, it either needs to be marked as a duplicate, or the
> other bug  should be marked as a duplicate of this one, sine this bug is
> older than the bug 50381. In any case the resolution as RESOLVED/FIXED is
> not appropriate here.

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.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.