[Bug 30259] StarCraft II doesn't start
wine-bugs at winehq.org
wine-bugs at winehq.org
Tue Mar 27 12:22:16 CDT 2012
http://bugs.winehq.org/show_bug.cgi?id=30259
--- Comment #11 from Austin English <austinenglish at gmail.com> 2012-03-27 12:22:16 CDT ---
(In reply to comment #10)
> (In reply to comment #9)
> > (In reply to comment #8)
> > This bug is closed as duplicate not invalid.
>
> _Now_, but that's not the first thing you did. The first thing you did was to
> mark it as INVALID without really knowing if was invalid or not; IOW without
> knowing if UseGLSL was the issue or not.
>
> vitaliy-bugzilla at kievinfo.com
> 2012-03-24 22:33:45 CDT
> Status UNCONFIRMED RESOLVED
> Resolution --- INVALID
>
> > What are you complaining about?
>
> ^- You are marking bugs as INVALID without knowing if they are really invalid.
>
> > That you did something Wine _explicitly told you_ not to do?
>
> Where?
>
> This is what Wine says: 'The GLSL shader backend has been disabled. You get to
> keep all the pieces if it breaks.'
>
> This didn't cause any issue. It's *totally* and *completely* irrelevant. I know
> because I tried disabling it, as I said in further comments. I should have lied
> and removed that line from the output.
The point, however, is we don't know that immediately. The configuration is
unsupported, it's a waste of time to attempt to find a valid bug in an
unsupported configuration. The burden is on you to attempt the application, in
a _supported_ way, not expect _volunteers_ to spend valuable time trying to
find if there is a valid bug. That time is better spent on well defined bugs.
> > And now you
> > getting a ear full of developers telling you why you shouldn't do it?
> >
> > Yes, your program has an issue running under Wine. Yes there is a bug about it
> > (bug 29982). Either wait for it to be resolved or fix it yourself for everyone
> > else to enjoy. Wine is an open source project. No one owes anything to anyone.
> > All people here are volunteers and contribute their own free time, experience
> > and knowledge to the project.
>
> Yes, that doesn't make your actions any more appropriate.
>
> Closing bugs for the wrong reasons is still wrong.
>
> If it makes you happier to close as INVALID all bugs that have UseGLSL
> disabled, go ahead, that doesn't help anybody, specially not the Wine project.
> What you should be doing is *first* make sure UseGLSL is the issue, and *then*
> mark as INVALID.
No, for reasons pointed out beforehand. For similar reasons, if someone reports
a bug and wine complains that their 3d setup is invalid (no direct rendering
support), we ask them to fix their setup first, to rule out that problem.
> But I'm sure you will never accept that there's room for improvement for your
> actions. No, you are perfect.
Everyone has room for improvement, but asking volunteer developers to change
their practices whenever you clearly didn't follow instructions is a bit
selfish.
Regardless, I'm done with this discussion, I have better uses for my time.
Regards,
Austin
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
More information about the wine-bugs
mailing list