[Bug 18935] Peachtree First Accounting 2010 install fails because it can't find AVManagerUnified.dll

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=18935

--- Comment #7 from Frédéric Delanoy <frederic.delanoy at gmail.com> 2013-05-10 04:12:40 CDT ---
(In reply to comment #6)
> Hello Frédéric,
> 
> why not?
> It took me some time to find something similar on the internet, to investigate
> the problem and even find new problems (-> new bug reports).

I appreciate the time you spent trying to find similar stuff on the internet
for sure, that was not my point.
I also spend some of my free time on bug reports, you know. 

> The product code base is the _same_, the installer technology is the _same_.
> See the trace log snippet where you can clearly see both dlls mentioned in 
> that bug report.

Well, the same dlls are mentioned, true, but you can't say that the "product
code base is the same", unless you have access to the source code (which I
suppose you don't).
There might be slight variations in the code bases that make the bug appear in
one app, and not in a similar app.

> Many bug reporters simply left the Wine project mainly because of real life,
> Dan is no exception here.

Well you closed the bug a mere *2* days after I added my comment: that's quite
a (too) short amount of time to react IMHO : that's why I reopened the bug.
It's always better to have the OP retest, if possible.

> These bugs are effectively abandoned until they get picked up by other people.
> Alternatively these bugs are simply closed by "x times no reaction -> abandon"
> sweeps which is of course the last resort.

True, if a bug can't be reproduced due to no download available, and no OP
reaction, there's not much one can do about the bug, besides closing it.

> From my point of view Wine Bugzilla is not really in a satisfactory state of
> affairs.
> 
> There are many hundreds, heck thousands of open bugs that are candidates for
> immediate close down (based on my experience) and nothing of value would be
> lost.
> Many of them are of poor quality, unwillingness/incapability of reporter to
> provide additional info, mixed up issues/contradicting info, abandoned software
> or already fixed.
> It takes time to understand what the reporter actually meant and to _find_
> applications to somehow reproduce the problem - years after the bug was
> created.
> 
> Do you want to put the people away that try to make an attempt to improve the
> situation?

Of course not. I'm sorry if you felt that way. That certainly wasn't my
intention.
There's no easy solution for the bad average bug quality, I'm afraid, short of
trying to "educate" users.
FWIW, I've also been "hurt" more than once by bad bugs, as many other
volunteers have also been.

> I can certainly push my own agenda (which I sometimes do), only
> reporting/working on bugs in my own interest.
> Although these are sometimes interesting things from technical perspective the
> number would be low.
> So guess what would be the greater loss?

Most (but not all) people work on bugs they care about. You know I don't
particularly care about this app either, yet I bothered to download hundreds of
megs, register, test and open a new bug (see comment 1).
I could as well have marked this bug "closed - abandoned" back then...

> But if you are inclined please feel free and notify Dan about _all_ his open
> bugs (several hundreds FYI) and ask him to do something about the situation.

Spamming him with hundreds of bug notification messages won't certainly help
the situation..

Regards,

-- 
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.