http://bugs.winehq.org/show_bug.cgi?id=18935
--- Comment #6 from Anastasius Focht focht@gmx.net 2013-05-10 03:21:44 CDT --- 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). 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.
Many bug reporters simply left the Wine project mainly because of real life, Dan is no exception here. 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.
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? 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?
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.
Regards