[Nouveau] [Bug 79266] [NVC1] GT 430 / GF108 sluggish, unstable performance and blue tint with vdpau

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79266

--- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to comment #4)
> Sorry, but I am just annoyed by your attitude. It is a bug that affects
> multiple things at once that are inconclusive each by themselves and you
> argue that you have to discard those kind of bugs because it conflicts with
> your problem solving approach... To put bluntly, it sounds like you are
> trying to grab excuses with your points a, b ,c and on top of all finish by
> telling me (in other words) "If I want help I should be less cocky about my
> problems." ....

I was merely making observations that I thought might help you out. They
didn't. There are two separate things... your problems, and your attitude. Your
problems are fine. I was suggesting taking a more collaborative and less
confrontational attitude. My goal here is to either get this bug into a state
where someone can do something (aka "actionable"), or to close it as invalid
because such a state is not achievable.

> 
> Someone just has to look at this in close detail, possibly testing with the
> hardware. Maybe that is not feasible to you currently, but it doesn't make
> the bug report invalid and it doesn't change that it is broken. If you can't
> fix it, you leave it, at least that's how I know bug reporting.

This approach, while initially friendlier to the bug submitter, leads to
enormous bug lists that nobody ever looks at, which in turn may as well not
exist. In the end, I believe that this does a disservice to bug submitters. I'm
trying to keep all of the open bugs actionable so that an interested party can
look and see what the things to do are. If you don't like my problem solving
approach, I would love nothing more than to hear a more effective one.

The way that resolving these issues tends to work is largely collaborative. You
have to describe the issues clearly, and perhaps do some tracing. If you're not
willing to help along, this issue becomes non-actionable (and thus invalid).

So.... let's start with the basics. Let's say I have a GT 430. What do I need
to do in order to reproduce one of the issues.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140526/25b08bcc/attachment.html>